edibble
A grammar for experimental design that learned to compose designs and track its own provenance.
A side-by-side editorial comparison of mcmcensemble and rrum — release velocity, themes, recent moves, and the top alternatives to consider.
An ensemble sampler just admitted its walkers were barely talking to each other.
mcmcensemble provides affine-invariant ensemble MCMC samplers — differential evolution and stretch move — behind a single MCMCEnsemble() entry point. The API consolidated in 3.0.0 around a flexible inits argument and a hidden internal surface, with parallelism delegated to the future framework. The 2025 release fixed a defect in the sampling behaviour itself, and results now differ from every earlier version.
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.
mcmcensemble provides affine-invariant ensemble MCMC samplers — differential evolution and stretch move — behind a single MCMCEnsemble() entry point. The API consolidated in 3.0.0 around a flexible inits argument and a hidden internal surface, with parallelism delegated to the future framework. The 2025 release fixed a defect in the sampling behaviour itself, and results now differ from every earlier version.
Development has moved from packaging to statistics. The early releases were about shape: a rename, argument alignment, moving coda to Suggests, adding tests, then parallel execution and named-vector support. The 3.0.0 release closed the API down to one wrapper and generalised initialisation. What is left, as 3.2.0 shows, is the correctness of the sampler itself — walker correlation, ergodicity checks, and grid artefacts in the differential evolution step were all addressed in a single release, all reported by one contributor. The package is being audited rather than extended.
Further sampler-behaviour fixes are the most likely next move, since three separate correctness issues surfaced together in the last release and the package's API has been stable since 3.0.0.
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 mcmcensemble 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 mcmcensemble 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. mcmcensemble 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. mcmcensemble 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 mcmcensemble alternatives in Analytics are ranked by recent ship velocity. Browse the "mcmcensemble alternatives" section above for the current picks, or visit /alternatives/mcmcensemble 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.