← Back to home
Comparison · Analytics

aniread vs rrum

A side-by-side editorial comparison of aniread and rrum — release velocity, themes, recent moves, and the top alternatives to consider.

aniread vs rrum: at a glance

Featureanireadrrum
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importpsychometrics, r-package, gibbs-sampling, maintenance
Last editorial update13h ago2d ago
WebsiteVisit →Visit →

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.

Read the full aniread trajectory →

What is rrum?

Six years past its API cleanup, rrum ships only what the compiler demands.

rrum estimates the reduced Reparameterized Unified Model via a Gibbs sampler in Rcpp/Armadillo, with simulation delegated to its sibling package simcdm. The user-facing API has been settled since 2019, when the entry point was renamed and simulation was moved out. Releases since then have been build and CRAN compliance work.

Read the full rrum trajectory →

aniread vs rrum: editorial side-by-side

A
aniread
ANALYTICS
3.8

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.

R
rrum
ANALYTICS
0.0

Six years past its API cleanup, rrum ships only what the compiler demands.

◆ Current state

rrum estimates the reduced Reparameterized Unified Model via a Gibbs sampler in Rcpp/Armadillo, with simulation delegated to its sibling package simcdm. The user-facing API has been settled since 2019, when the entry point was renamed and simulation was moved out. Releases since then have been build and CRAN compliance work.

◆ Where it's heading

The arc runs from an API-breaking consolidation in 2019, through a 2023 release fixing C++ deprecations and adding a pkgdown site, to a 2025 maintenance release that raises dependency floors and swaps a deprecated Armadillo conversion call. Each release is triggered by something outside the package — R-devel, CRAN check notes, an Armadillo deprecation — rather than by modeling work. The 2025 release arrived the same morning as a near-identical one for edina, marking it as a maintainer-wide sweep across the lab's packages.

◆ Prediction

The next release will most likely be another externally forced compatibility fix, since three consecutive releases have been reactions to toolchain deprecations rather than to user requests.

Alternatives to aniread and rrum

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 rrum.

See all aniread alternatives → · See all rrum alternatives →

Recent activity from aniread and rrum

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 23h agoanireadv0.6.0 — one entry point for every format
  2. 1mo agoanireadget_supported_sources(); Octron gap and BORIS index fixes
  3. 1mo agoanireadread_boris() imports behavioural events as anievent objects
  4. 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
  5. 3mo agoaniready-origin standardised to bottom-left across eleven readers
  6. 10mo agorrumrrum 0.2.2 - Maintenance Release
  7. 2y agorrumR-devel C++ fixes, pkgdown site, CI moved to GitHub Actions
  8. 7y agorrumCRAN release breaks the API and moves simulation to simcdm

Frequently asked questions

What is the difference between aniread and rrum?

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 rrum?

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 rrum?

Top rrum alternatives in Analytics are ranked by recent ship velocity. Browse the "rrum alternatives" section above for the current picks, or visit /alternatives/rrum for the full list with editorial commentary on each.