RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
Comparison · Analytics
modeltime.resample vs npi
A side-by-side editorial comparison of modeltime.resample and npi — release velocity, themes, recent moves, and the top alternatives to consider.
modeltime.resample vs npi: at a glance
What is modeltime.resample?
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.
What is npi?
An R client for the US provider registry, tightening its types and edge-case handling
npi wraps the US National Provider Identifier registry API for R users, covering search, validation and summarisation of provider records. The one release in view is a consolidation pass rather than new surface: input normalisation, vectorised validation, and a typed empty result instead of an ambiguous one when a search finds nothing.
modeltime.resample vs npi: editorial side-by-side
modeltime.resample
0.0ANALYTICS
modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect the next release to track the next tidymodels breaking change, with any new work continuing on error reporting rather than resampling strategies.
npi
0.0ANALYTICS
An R client for the US provider registry, tightening its types and edge-case handling
◆ Current state
npi wraps the US National Provider Identifier registry API for R users, covering search, validation and summarisation of provider records. The one release in view is a consolidation pass rather than new surface: input normalisation, vectorised validation, and a typed empty result instead of an ambiguous one when a search finds nothing.
◆ Where it's heading
The work is aimed at making the package behave predictably inside larger pipelines. Returning a typed empty `npi_results` object on no matches, and having `npi_is_valid()` accept vectors and return logical vectors, both remove branches a caller would otherwise write by hand. The bug fix follows the same line — `npi_summarize()` no longer drops input rows when a record's nested address or taxonomy data is missing.
◆ Prediction
With a single release visible there is not enough of a pattern to predict a direction confidently; the changes here suggest continued interface tidying rather than new API coverage, but that is one data point.
Alternatives to modeltime.resample and npi
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 npi.
geoarrow-r
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all modeltime.resample alternatives → · See all npi alternatives →
Recent activity from modeltime.resample and npi
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agonpiVectorised validation and typed empty search results
- 11mo agomodeltime.resampletune 2.0 support, deterministic seeding, clearer errors
- 11mo agomodeltime.resampleDependency cleanup ahead of the next tune release
- 3y agomodeltime.resampleFixes workflows in regression mode
- 4y agomodeltime.resampleUpdates for hardhat 1.0.0
Frequently asked questions
What is the difference between modeltime.resample and npi?
They serve adjacent needs but don't currently overlap on shipped themes. modeltime.resample and npi 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.
Is modeltime.resample better than npi?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. modeltime.resample and npi 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.
What are the best alternatives to modeltime.resample?
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.
What are the best alternatives to npi?
Top npi alternatives in Analytics are ranked by recent ship velocity. Browse the "npi alternatives" section above for the current picks, or visit /alternatives/npi-r for the full list with editorial commentary on each.