tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of errors and mrbayes — release velocity, themes, recent moves, and the top alternatives to consider.
errors keeps making uncertainty print the way each scientific field expects.
errors attaches uncertainty to numeric vectors and propagates it automatically through arithmetic, as part of the r-quantities family alongside units. The propagation core is settled; recent releases concentrate on presentation and integration — PDG rounding rules in 0.4.2, decimal support in parenthesis notation in 0.4.3, and ggplot2 deprecation tracking in 0.4.1 and 0.4.4.
mrbayes spent 2026 auditing its own Bayesian MR estimators for coding errors.
mrbayes wraps Stan and JAGS implementations of Bayesian Mendelian randomization estimators — IVW, MR-Egger, radial Egger, and their multivariable forms. Most of the visible history is packaging work: dependency trimming, conditional examples so the package installs where JAGS will not compile, a maintainer handover. The 0.5.3 release in July 2026 breaks that pattern with a dense list of fixes inside the model code itself.
errors attaches uncertainty to numeric vectors and propagates it automatically through arithmetic, as part of the r-quantities family alongside units. The propagation core is settled; recent releases concentrate on presentation and integration — PDG rounding rules in 0.4.2, decimal support in parenthesis notation in 0.4.3, and ggplot2 deprecation tracking in 0.4.1 and 0.4.4.
Two threads run through this history. One is formatting convergence: uncertainty has field-specific conventions, and the package has been absorbing them one contributed pull request at a time rather than imposing a single style. The other is keeping the errors class first-class everywhere R users work — vctrs methods for dplyr 1.0, a geom_errors() layer for ggplot2, missing-value and duplicate handling. Both are integration work, which is what a type-extension package mostly is.
Expect further formatting conventions to arrive as contributions, following PDG rounding and the decimals option, plus continued upkeep against ggplot2 aesthetic deprecations that have forced two of the last four releases.
mrbayes wraps Stan and JAGS implementations of Bayesian Mendelian randomization estimators — IVW, MR-Egger, radial Egger, and their multivariable forms. Most of the visible history is packaging work: dependency trimming, conditional examples so the package installs where JAGS will not compile, a maintainer handover. The 0.5.3 release in July 2026 breaks that pattern with a dense list of fixes inside the model code itself.
The package has moved from packaging upkeep into a correctness-audit phase. 0.5.3 fixes a hardcoded three-exposure loop in MVMR-Egger reporting, a broken joint-prior branch, a sigma parameterization error in radial Egger, and several prior specifications — the profile of a maintainer reading their own model files closely rather than responding to bug reports. Platform work continues underneath: an R 4.3.0 floor inherited through a transitive dependency chain, and segfault fixes on macOS ARM.
Expect further audit-driven patches to the remaining rjags and Stan model files rather than new estimators; the fixes in 0.5.3 cluster in the Egger variants, which suggests that is where the reading is still in progress.
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 errors or mrbayes.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
See all errors alternatives → · See all mrbayes alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. errors and mrbayes 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. errors and mrbayes 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 errors alternatives in Analytics are ranked by recent ship velocity. Browse the "errors alternatives" section above for the current picks, or visit /alternatives/errors-r for the full list with editorial commentary on each.
Top mrbayes alternatives in Analytics are ranked by recent ship velocity. Browse the "mrbayes alternatives" section above for the current picks, or visit /alternatives/mrbayes for the full list with editorial commentary on each.