Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of aniread and rmediation — release velocity, themes, recent moves, and the top alternatives to consider.
aniread stops asking you to know which tracker wrote the file
aniread is the reader package of the animovement suite, importing output from pose-estimation, centroid and behavioural-scoring tools into aniframe objects. Through 0.5.x the work was per-reader: get_supported_sources() exposed the format list programmatically, read_boris() added behavioural events, and Octron and BORIS each got targeted fixes. 0.6.0 changes the shape of the interface itself — read_dataset() takes any supported file through one entry point and detect_source() works out which software wrote it by inspecting contents, not just the suffix.
RMediation shipped a three-normal CDF, then found it was silently wrong.
RMediation is a long-standing CRAN package for confidence intervals on mediated effects, now built on an S7 class hierarchy. Over eight weeks it added ProductNormal3 for serial indirect effects of the form a1*a2*b, folded the engine into the existing pprodnormal naming family, and then replaced that engine outright after finding it returned wrong probabilities without warning. The dev branch is at 1.7.0; CRAN still serves 1.6.1.
aniread is the reader package of the animovement suite, importing output from pose-estimation, centroid and behavioural-scoring tools into aniframe objects. Through 0.5.x the work was per-reader: get_supported_sources() exposed the format list programmatically, read_boris() added behavioural events, and Octron and BORIS each got targeted fixes. 0.6.0 changes the shape of the interface itself — read_dataset() takes any supported file through one entry point and detect_source() works out which software wrote it by inspecting contents, not just the suffix.
The package is moving from a set of named readers to a dispatcher with the readers behind it, and the hard part is being handled rather than hidden: twelve sources emit .csv, so detection narrows by suffix then inspects content, and DeepLabCut and LightningPose files are structurally identical so it returns the combined 'deeplabcut/lightningpose' rather than guessing wrong. The honesty extends to gaps — optional-dependency detectors are skipped when the package is absent and the error names what was skipped, and SLEAP's csv suffix was withdrawn because auto-detection would have routed files into a reader that cannot read them. Alongside this, read_trackball() was substantially repaired for real two-sensor Bonsai captures, where alignment, clocks, corrupt rows and gap filling were each independently wrong.
Expect the withdrawn SLEAP csv suffix to return once read_sleap() gains support, since the changelog explicitly parks it against issue #87. Further detectors are the natural next increment, and the sensor-local-clock warning class suggests trackball alignment is not finished.
RMediation is a long-standing CRAN package for confidence intervals on mediated effects, now built on an S7 class hierarchy. Over eight weeks it added ProductNormal3 for serial indirect effects of the form a1*a2*b, folded the engine into the existing pprodnormal naming family, and then replaced that engine outright after finding it returned wrong probabilities without warning. The dev branch is at 1.7.0; CRAN still serves 1.6.1.
The package is moving from a hand-rolled numerical layer to one that checks itself: the new default integrator escalates its node count until successive rules agree, warns when it hits the cap instead of returning a number, and exposes a diagnostics argument for the convergence estimate. The correctness fix went to dev ahead of the CRAN window rather than being held for it, which suggests wrong-answer bugs are treated as release-blocking regardless of cadence. Serial mediation is where the new surface area is concentrated.
1.7.0 exists specifically to land before CRAN's 2026-08-21 update window, so the next move is a CRAN submission promoting it to main; whether hcubature survives past that as a cross-check option is the open question.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either aniread or rmediation.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI spends a release unblocking queues and hardening upserts
See all aniread alternatives → · See all rmediation alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r package — within Analytics. aniread and rmediation are shipping at a similar cadence (velocity 3.8 vs 3.8, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aniread and rmediation are shipping at a similar cadence (velocity 3.8 vs 3.8, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top aniread alternatives in Analytics are ranked by recent ship velocity. Browse the "aniread alternatives" section above for the current picks, or visit /alternatives/aniread for the full list with editorial commentary on each.
Top rmediation alternatives in Analytics are ranked by recent ship velocity. Browse the "rmediation alternatives" section above for the current picks, or visit /alternatives/rmediation for the full list with editorial commentary on each.