edibble
A grammar for experimental design that learned to compose designs and track its own provenance.
A side-by-side editorial comparison of rolap and rrum — release velocity, themes, recent moves, and the top alternatives to consider.
A star-schema modelling package grew a query language, a deployment path, and then a map layer.
rolap builds dimensional models — star databases and constellations — from flat tables inside R. Over 2023 it acquired a multidimensional query interface, the ability to deploy models into relational databases, incremental refresh, and geographic layers exportable as GeoPackage. Since early 2024 it has been quiet, with the only 2025 release removing a test that clashed with another package.
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.
rolap builds dimensional models — star databases and constellations — from flat tables inside R. Over 2023 it acquired a multidimensional query interface, the ability to deploy models into relational databases, incremental refresh, and geographic layers exportable as GeoPackage. Since early 2024 it has been quiet, with the only 2025 release removing a test that clashed with another package.
The 2023 releases trace a deliberate progression from modelling to operating: first a common data model and flat table class, then role-playing dimensions, then incremental refresh, then querying and deployment, then geography, then slowly changing dimensions. That is essentially the feature checklist of a data warehouse, assembled in about six months and documented with a vignette at each step. The pace since has dropped to almost nothing, which reads as a project that reached its intended scope rather than one that stalled.
Given eighteen months in which the only release was a test removal, the next release is more likely to be maintenance than another warehouse feature — though the entries give no clear signal either way.
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 rolap 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 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.
PACTA's climate-alignment charting layer split prep from plotting, then settled into stable.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. rolap 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. rolap 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 rolap alternatives in Analytics are ranked by recent ship velocity. Browse the "rolap alternatives" section above for the current picks, or visit /alternatives/rolap 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.