RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of modeltime.resample and shapviz — release velocity, themes, recent moves, and the top alternatives to consider.
modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.
modeltime.resample runs time series cross-validation over modeltime models, returning per-resample predictions and accuracy plots. Version 0.3.0 is the substantive release in view: tune 2.0.0 compatibility, deterministic seeding via withr, guaranteed .predictions output, and clearer failures when resample fits break. The three releases before it are dependency chores.
shapviz refines its SHAP plots release by release while chasing ggplot2's moving target.
shapviz turns SHAP values from XGBoost, LightGBM, H2O, kernelshap and other sources into standard diagnostic plots — importance, dependence, waterfall, force and interaction. Recent work is plot ergonomics: shared y-axis control across dependence plots, a bar view for interaction values, and axis collection via patchwork. The two most recent releases are pure compatibility and bug fixes.
modeltime.resample runs time series cross-validation over modeltime models, returning per-resample predictions and accuracy plots. Version 0.3.0 is the substantive release in view: tune 2.0.0 compatibility, deterministic seeding via withr, guaranteed .predictions output, and clearer failures when resample fits break. The three releases before it are dependency chores.
Every entry here is compatibility work against something upstream — hardhat 1.0.0, workflows regression mode, then tune 2.0.0 twice. The 0.3.0 notes show a second concern emerging alongside it: making failures legible, with .notes on failed fits, actionable errors from unnest_modeltime_resamples(), and fallback logic when prediction columns go missing across versions. Reproducibility gets the same treatment through explicit seeding.
Expect the next release to track the next tidymodels breaking change, with any new work continuing on error reporting rather than resampling strategies.
shapviz turns SHAP values from XGBoost, LightGBM, H2O, kernelshap and other sources into standard diagnostic plots — importance, dependence, waterfall, force and interaction. Recent work is plot ergonomics: shared y-axis control across dependence plots, a bar view for interaction values, and axis collection via patchwork. The two most recent releases are pure compatibility and bug fixes.
Two threads run in parallel here. One is visual refinement converging on conventions from Python's shap — the 0.10.0 notes openly float switching share_y to TRUE to match it. The other is connector maintenance, keeping pace with H2O, XGBoost 1.x and 2.x, shapr and permshap as each changes. Neither thread adds new explanation methods; shapviz's job is presentation, and it is being polished rather than extended.
Expect share_y = TRUE to become the default and further ggplot2 4.x fallout, with connector updates arriving as the upstream SHAP packages release.
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 modeltime.resample or shapviz.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all modeltime.resample alternatives → · See all shapviz alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r package — within Analytics. modeltime.resample and shapviz 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. modeltime.resample and shapviz 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 modeltime.resample alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime.resample alternatives" section above for the current picks, or visit /alternatives/modeltime-resample for the full list with editorial commentary on each.
Top shapviz alternatives in Analytics are ranked by recent ship velocity. Browse the "shapviz alternatives" section above for the current picks, or visit /alternatives/shapviz for the full list with editorial commentary on each.