OHPL
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A side-by-side editorial comparison of RMVMR and treeshap — release velocity, themes, recent moves, and the top alternatives to consider.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
RMVMR provides radial multivariable Mendelian randomization — radial IVW estimation and plots layered over the MVMR package's conditional instrument-strength machinery. It has no independent release schedule: versions arrive alongside MVMR's, pin a minimum MVMR version, and fix defects in the seam between the two. Its most recent release landed the same day as new versions of MVMR and OneSampleMR.
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.
RMVMR provides radial multivariable Mendelian randomization — radial IVW estimation and plots layered over the MVMR package's conditional instrument-strength machinery. It has no independent release schedule: versions arrive alongside MVMR's, pin a minimum MVMR version, and fix defects in the seam between the two. Its most recent release landed the same day as new versions of MVMR and OneSampleMR.
The work is code hygiene with results held fixed. ivw_rmvmr() now fits the radial IVW model explicitly rather than inheriting variables left over from the orientation loop, an undocumented data element carrying unused intermediate frames is gone, and plot_rmvmr() stops recomputing univariate radial analyses it already has — roughly halving the RadialMR calls with identical output. Each note is explicit that coefficients, standard errors and degrees of freedom are unchanged, which is a deliberate contrast with MVMR's own 2026 releases, where several fixes did change reported values.
Because the package pins MVMR versions rather than vendoring behaviour, the next release most likely follows MVMR's next correctness fix; nothing in the notes points to independent feature work.
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 RMVMR or treeshap.
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A fast dplyr stand-in that keeps finding new places to skip work entirely.
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
A discrete global grid generator grew cell traversal and became a usable spatial index.
Community ecology's standard toolkit is retiring the functions a generation of scripts was built on.
See all RMVMR 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. RMVMR 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. RMVMR 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 RMVMR alternatives in Analytics are ranked by recent ship velocity. Browse the "RMVMR alternatives" section above for the current picks, or visit /alternatives/rmvmr 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.