edibble
A grammar for experimental design that learned to compose designs and track its own provenance.
A side-by-side editorial comparison of r2dii.plot and rrum — release velocity, themes, recent moves, and the top alternatives to consider.
PACTA's climate-alignment charting layer split prep from plotting, then settled into stable.
r2dii.plot renders the standard PACTA climate-alignment charts — trajectory, tech mix, emission intensity — as ggplot2 objects, paired with the 2DII colour palettes and theme. Since 0.4.0 the package has exposed a two-step pipeline where prep_*() shapes the data before plot_*() draws it, while qplot_*() remains the one-call convenience path. It declared itself stable in early 2025.
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.
r2dii.plot renders the standard PACTA climate-alignment charts — trajectory, tech mix, emission intensity — as ggplot2 objects, paired with the 2DII colour palettes and theme. Since 0.4.0 the package has exposed a two-step pipeline where prep_*() shapes the data before plot_*() draws it, while qplot_*() remains the one-call convenience path. It declared itself stable in early 2025.
The package has been converging on a settled contract for years. Early releases chased visual polish and label handling, then 0.2.0 exposed the palette scales as reusable ggplot2 components, and 0.4.0 made the prepared data a first-class artefact rather than something hidden inside a plotting call. Recent releases are documentation and hygiene: a data_dictionary describing every column, definitions filled in, demo datasets renamed to say they are demos. It also moved organisations, from 2DII to RMI-PACTA, and its releases stay pinned to r2dii.analysis and to ggplot2's deprecation schedule.
With the lifecycle marked stable and the last two releases confined to dataset naming and documentation, the next release is most likely another ggplot2 compatibility pass or a sibling-package alignment rather than new chart types.
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 r2dii.plot 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.
See all r2dii.plot alternatives → · See all rrum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. r2dii.plot 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. r2dii.plot 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 r2dii.plot alternatives in Analytics are ranked by recent ship velocity. Browse the "r2dii.plot alternatives" section above for the current picks, or visit /alternatives/r2dii-plot 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.