silx
silx settles into maintenance a release after its PySide6 migration
A side-by-side editorial comparison of aniread and cfrnow — 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.
A Bayesian real-time CFR estimator that now ships stratified fits and posterior-predictive checks
cfrnow estimates case fatality ratios from line-list data while an outbreak is still running, using a Bayesian mixture-cure survival model registered as an `epidist` model type. Three releases in a month took it from first public release to stratified, partially-pooled fits with posterior-predictive checking. It leans on `distspec` for delay parameterisation, which reached CRAN alongside the 0.2.1 patch.
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.
cfrnow estimates case fatality ratios from line-list data while an outbreak is still running, using a Bayesian mixture-cure survival model registered as an `epidist` model type. Three releases in a month took it from first public release to stratified, partially-pooled fits with posterior-predictive checking. It leans on `distspec` for delay parameterisation, which reached CRAN alongside the 0.2.1 patch.
The arc runs from producing a single corrected CFR number toward supporting a full model-checking workflow. 0.2.0 added the pieces a modeller needs to defend an estimate: replicate line lists replayed through the real-time truncation, an ascertainment-ratio correction for when fatal and non-fatal cases enter the line list at different rates, and per-group CFRs from `brms` formulas. Delay coverage widened from LogNormal and Gamma to Weibull in the same release.
Expect the next release to keep widening covariate and pooling support rather than adding new outcome types, since every 0.2.0 addition extended the existing formula interface instead of replacing it.
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 cfrnow.
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 cfrnow alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cfrnow is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. 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. cfrnow is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. 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 cfrnow alternatives in Analytics are ranked by recent ship velocity. Browse the "cfrnow alternatives" section above for the current picks, or visit /alternatives/cfrnow for the full list with editorial commentary on each.