silx
silx settles into maintenance a release after its PySide6 migration
Comparison · Analytics
aniread vs rlistings
A side-by-side editorial comparison of aniread and rlistings — release velocity, themes, recent moves, and the top alternatives to consider.
aniread vs rlistings: at a glance
What is aniread?
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.
What is rlistings?
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
rlistings renders clinical-trial subject listings and paginates them for regulatory output, sitting alongside rtables on the shared formatters engine. The releases in this window are dominated by pagination correctness: repeated key columns across pages, splitting by a variable, ordered-factor handling, column gaps, and font metrics. Development is a large rotating contributor set inside the insightsengineering organisation.
aniread vs rlistings: editorial side-by-side
aniread
3.8ANALYTICS
aniread stops asking you to know which tracker wrote the file
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
rlistings
0.0ANALYTICS
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
◆ Current state
rlistings renders clinical-trial subject listings and paginates them for regulatory output, sitting alongside rtables on the shared formatters engine. The releases in this window are dominated by pagination correctness: repeated key columns across pages, splitting by a variable, ordered-factor handling, column gaps, and font metrics. Development is a large rotating contributor set inside the insightsengineering organisation.
◆ Where it's heading
The package is progressively delegating pagination to formatters rather than implementing it — paginate_listing() was refactored to call formatters' paginate_to_mpfs() directly, and truetype font support arrived through a new formatters API. That reduces duplicated logic but ties the package's page-break behaviour to a dependency it shares with rtables. Feature work beyond pagination is thin: better error messages for unsupported column classes, a cheatsheet.
◆ Prediction
Expect pagination fidelity to remain the focus, with changes arriving as formatters exposes more of its layout machinery rather than as rlistings-native features.
Alternatives to aniread and rlistings
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 rlistings.
Plotly
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
Rho
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI
OpenCTI spends a release unblocking queues and hardening upserts
Grafana Mimir
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 rlistings alternatives →
Recent activity from aniread and rlistings
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 19h agoanireadv0.6.0 — one entry point for every format ⚡
- 1mo agoanireadget_supported_sources(); Octron gap and BORIS index fixes
- 1mo agoanireadread_boris() imports behavioural events as anievent objects
- 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
- 3mo agoaniready-origin standardised to bottom-left across eleven readers ⚡
- 1y agorlistingsError and message handling for difftime and zero-row listings
- 1y agorlistingsTrueType font support and col_gap in pagination
- 2y agorlistingssplit_into_pages_by_var() and pagination moved onto formatters
Frequently asked questions
What is the difference between aniread and rlistings?
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.
Is aniread better than rlistings?
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.
What are the best alternatives to aniread?
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.
What are the best alternatives to rlistings?
Top rlistings alternatives in Analytics are ranked by recent ship velocity. Browse the "rlistings alternatives" section above for the current picks, or visit /alternatives/rlistings for the full list with editorial commentary on each.