tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of errors and treeshap — 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.
treeshap keeps widening its tree-model coverage while the SHAP math stays put.
treeshap computes exact SHAP values for tree ensembles in R, reaching each modelling framework through a per-framework unify() adapter. Since returning to CRAN in 2023 it has added GPBoost, ranger survival forests and multi-output models to that adapter layer. Four releases in three years, each dominated by adapter work contributed by users of one specific framework.
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.
treeshap computes exact SHAP values for tree ensembles in R, reaching each modelling framework through a per-framework unify() adapter. Since returning to CRAN in 2023 it has added GPBoost, ranger survival forests and multi-output models to that adapter layer. Four releases in three years, each dominated by adapter work contributed by users of one specific framework.
The direction is breadth of model support rather than new explanation methods: every release since the first CRAN submission adds or repairs a unify() backend. Maintenance is community-driven, with named contributors fixing the framework they personally use. Nothing in these entries points at work on the SHAP algorithms themselves.
Expect the next release to add or repair another unify() adapter as a contributor brings their own framework, rather than to change how explanations are computed.
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 treeshap.
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 treeshap 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 treeshap 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 treeshap 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 treeshap alternatives in Analytics are ranked by recent ship velocity. Browse the "treeshap alternatives" section above for the current picks, or visit /alternatives/treeshap for the full list with editorial commentary on each.