RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of modeltime.resample and monitOS — 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.
monitOS relicenses to MIT, the clearest signal in a sparse Novartis release feed.
monitOS is Novartis's R package for monitoring overall survival in clinical trials, with an accompanying Shiny app. The 0.1.6 release changes the licence to MIT, fixes a shiny import problem and an infinite-value bug in the app, and adds spell checking plus issue-tracker and website links. The prior release carries no notes at all beyond a link to the commit history.
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.
monitOS is Novartis's R package for monitoring overall survival in clinical trials, with an accompanying Shiny app. The 0.1.6 release changes the licence to MIT, fixes a shiny import problem and an infinite-value bug in the app, and adds spell checking plus issue-tracker and website links. The prior release carries no notes at all beyond a link to the commit history.
For a package published by a pharmaceutical sponsor, the licence change is the substantive item — MIT removes friction for reuse outside Novartis, and the added issue link and website point the same way, toward outside users. Everything else is packaging hygiene. At 0.1.6 with two releases nine months apart, the statistical methodology looks settled while the distribution around it is being tidied.
The open-sourcing signals suggest the next release will respond to outside issue reports; the entries give no indication of methodology changes.
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 monitOS.
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 monitOS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. modeltime.resample and monitOS 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 monitOS 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 monitOS alternatives in Analytics are ranked by recent ship velocity. Browse the "monitOS alternatives" section above for the current picks, or visit /alternatives/monitos for the full list with editorial commentary on each.