← Back to home
Comparison · Analytics

edibble vs mcmcensemble

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

Shared themes:reproducibilityr-package

edibble vs mcmcensemble: at a glance

Featureedibblemcmcensemble
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesexperimental-design, grammar-of-design, reproducibility, simulationmcmc, bayesian-inference, ensemble-sampling, reproducibility
Last editorial update30m ago38m ago
WebsiteVisit →Visit →

What is edibble?

A grammar for experimental design that learned to compose designs and track its own provenance.

edibble expresses experimental designs declaratively — units, treatments, records and their allotments — rather than calling a canned design function. Since 1.0.0 its internals run on a Provenance object that records the commands used to build a design, and 1.1.0 added conditional treatments, design composition and a separated simulation step. Recent work has focused on designs constructed from existing data rather than from scratch.

Read the full edibble trajectory →

What is mcmcensemble?

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.

Read the full mcmcensemble trajectory →

edibble vs mcmcensemble: editorial side-by-side

E
edibble
ANALYTICS
0.0

A grammar for experimental design that learned to compose designs and track its own provenance.

◆ Current state

edibble expresses experimental designs declaratively — units, treatments, records and their allotments — rather than calling a canned design function. Since 1.0.0 its internals run on a Provenance object that records the commands used to build a design, and 1.1.0 added conditional treatments, design composition and a separated simulation step. Recent work has focused on designs constructed from existing data rather than from scratch.

◆ Where it's heading

Development has moved from vocabulary to composition. Early releases established the core grammar; 1.0.0 replaced the internal R6 machinery with a Provenance object that tracks both internal and external commands, which is what lets a design carry its own construction history. On that foundation 1.1.0 added the ability to add two designs together, express conditional treatment structures, and split simulation specification from execution. The 2025 release turns toward a different entry point — wiring up level edges and unit attributes when an edibble object is built from data that already exists, rather than from a design declared up front.

◆ Prediction

Expect continued work on designs derived from existing data, since that is where the last release concentrated and it is the path least covered by the declarative grammar.

M
mcmcensemble
ANALYTICS
0.0

An ensemble sampler just admitted its walkers were barely talking to each other.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to edibble and mcmcensemble

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 edibble or mcmcensemble.

See all edibble alternatives → · See all mcmcensemble alternatives →

Recent activity from edibble and mcmcensemble

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

  1. 1y agomcmcensembleWalker correlation bug fixed, changing results at any seed
  2. 1y agoedibbleBetter handling of designs built from existing data
  3. 2y agomcmcensembleClearer error when only one walker is supplied
  4. 2y agomcmcensembleAPI narrows to one entry point with flexible initialisation
  5. 2y agoedibbleedibble 1.1.0
  6. 2y agoedibbleInternals rebuilt on a command-tracking Provenance object
  7. 3y agoedibbleS3 consistency and citation modernised
  8. 3y agoedibbleRd files fixed for HTML5 compatibility
  9. 4y agoedibbleInitial release
  10. 5y agomcmcensembleNamed parameter vectors and recorded sampler metadata
  11. 5y agomcmcensembleParallel ensemble sampling via the future framework
  12. 5y agomcmcensemblePackage renamed to mcmcensemble with aligned arguments and tests

Frequently asked questions

What is the difference between edibble and mcmcensemble?

Both compete on the same themes — reproducibility, r-package — within Analytics. edibble and mcmcensemble 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.

Is edibble better than mcmcensemble?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. edibble and mcmcensemble 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.

What are the best alternatives to edibble?

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

What are the best alternatives to mcmcensemble?

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.