silx
silx settles into maintenance a release after its PySide6 migration
A side-by-side editorial comparison of aniread and r2dii.plot — 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.
PACTA's climate-alignment charting layer split prep from plotting, then settled into stable.
r2dii.plot renders the standard PACTA climate-alignment charts — trajectory, tech mix, emission intensity — as ggplot2 objects, paired with the 2DII colour palettes and theme. Since 0.4.0 the package has exposed a two-step pipeline where prep_*() shapes the data before plot_*() draws it, while qplot_*() remains the one-call convenience path. It declared itself stable in early 2025.
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.
r2dii.plot renders the standard PACTA climate-alignment charts — trajectory, tech mix, emission intensity — as ggplot2 objects, paired with the 2DII colour palettes and theme. Since 0.4.0 the package has exposed a two-step pipeline where prep_*() shapes the data before plot_*() draws it, while qplot_*() remains the one-call convenience path. It declared itself stable in early 2025.
The package has been converging on a settled contract for years. Early releases chased visual polish and label handling, then 0.2.0 exposed the palette scales as reusable ggplot2 components, and 0.4.0 made the prepared data a first-class artefact rather than something hidden inside a plotting call. Recent releases are documentation and hygiene: a data_dictionary describing every column, definitions filled in, demo datasets renamed to say they are demos. It also moved organisations, from 2DII to RMI-PACTA, and its releases stay pinned to r2dii.analysis and to ggplot2's deprecation schedule.
With the lifecycle marked stable and the last two releases confined to dataset naming and documentation, the next release is most likely another ggplot2 compatibility pass or a sibling-package alignment rather than new chart types.
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 r2dii.plot.
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
Mimir's feed is a weekly Helm bot, with the 3.2 candidate the only real release in months
See all aniread alternatives → · See all r2dii.plot alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. aniread is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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 is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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 r2dii.plot alternatives in Analytics are ranked by recent ship velocity. Browse the "r2dii.plot alternatives" section above for the current picks, or visit /alternatives/r2dii-plot for the full list with editorial commentary on each.