edibble
A grammar for experimental design that learned to compose designs and track its own provenance.
A side-by-side editorial comparison of remora and rrum — release velocity, themes, recent moves, and the top alternatives to consider.
Australia's animal-tracking QC toolkit added a global 3-D ocean dataset, then spent two years absorbing upstream churn.
remora quality-controls acoustic telemetry detections from the IMOS Animal Tracking Facility and joins them to environmental data. Its capability surface settled with the 0.8-0 release, which added Bluelink reanalysis access and an interactive QC plot. Since then the work has been keeping data access fast and correct as the upstream providers change underneath it.
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.
remora quality-controls acoustic telemetry detections from the IMOS Animal Tracking Facility and joins them to environmental data. Its capability surface settled with the 0.8-0 release, which added Bluelink reanalysis access and an interactive QC plot. Since then the work has been keeping data access fast and correct as the upstream providers change underneath it.
The package's releases are paced by its dependencies rather than by feature ambition. The 2023 release had to survive the retirement of rgeos and rgdal — an ecosystem-wide deadline that forced every R spatial package to rebuild — and used the same release to add real capability. The 2025 release is entirely reactive in a different way, tracking an AODN metadata schema change that split one project-name field into two and swapping in tidync for faster environmental downloads. For a tool bound to a national data facility, schema changes at the source are the main release trigger.
Expect the next release to track further IMOS or AODN metadata changes and continue tuning environmental data access, since two consecutive releases have been driven by upstream schema and package retirements rather than new analysis features.
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.
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.
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.
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 remora or rrum.
A grammar for experimental design that learned to compose designs and track its own provenance.
A Swiss clinical-trial data reader that surfaces once every couple of years to clear check notes.
Brazil's flight-data package keeps working around what ANAC publishes and when.
A star-schema modelling package grew a query language, a deployment path, and then a map layer.
A water-research lab's ODBC helper, still fighting Windows database drivers a decade in.
PACTA's loan-book matcher opened up to sector taxonomies other than its own.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. remora and rrum are shipping at a similar cadence (velocity 0.0 vs 0.0, 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. remora and rrum are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top remora alternatives in Analytics are ranked by recent ship velocity. Browse the "remora alternatives" section above for the current picks, or visit /alternatives/remora for the full list with editorial commentary on each.
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.