edibble
A grammar for experimental design that learned to compose designs and track its own provenance.
A side-by-side editorial comparison of hubVis and mcmcensemble — release velocity, themes, recent moves, and the top alternatives to consider.
The hubverse plotting layer spends its releases absorbing upstream churn, not adding charts.
hubVis is the visualization component of the hubverse stack, centred on plot_step_ahead_model_output() for static and interactive forecast plots. Since the stable 0.1.0 in late 2024 it has shipped three patch releases, every one of them a single referenced issue fix. The plotting surface itself has not grown.
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.
hubVis is the visualization component of the hubverse stack, centred on plot_step_ahead_model_output() for static and interactive forecast plots. Since the stable 0.1.0 in late 2024 it has shipped three patch releases, every one of them a single referenced issue fix. The plotting surface itself has not grown.
The pattern across all four releases is narrow and reactive: a legend construction fix, a palette assignment fix, and most recently a compatibility change for ggplot2 4.0.0 written to keep working with earlier versions too. Two of the three fixes concern colour and legend handling, which suggests palette assignment is the fragile part of the codebase. As a thin layer over ggplot2 inside a larger stack, the package's release triggers come from below it rather than from its own roadmap.
Expect continued single-issue patches driven by upstream ggplot2 changes and by whatever the sibling hubverse packages emit, rather than new plot types.
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.
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 hubVis or mcmcensemble.
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 hubVis alternatives → · See all mcmcensemble alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. hubVis 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. hubVis 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.
Top hubVis alternatives in Analytics are ranked by recent ship velocity. Browse the "hubVis alternatives" section above for the current picks, or visit /alternatives/hubvis for the full list with editorial commentary on each.
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.