qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of modeltime.resample and tern.rbmi — 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.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
tern.rbmi renders the output of {rbmi} reference-based multiple imputation analyses into tern tables for clinical reporting. Its three most recent releases exist to satisfy CRAN: restricting vignette builds to gcc, adding V8 to Suggests, and a plain resubmission. No user-facing functionality has changed in the visible window, and the three older entries now backfilled are version-bump automation.
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.
tern.rbmi renders the output of {rbmi} reference-based multiple imputation analyses into tern tables for clinical reporting. Its three most recent releases exist to satisfy CRAN: restricting vignette builds to gcc, adding V8 to Suggests, and a plain resubmission. No user-facing functionality has changed in the visible window, and the three older entries now backfilled are version-bump automation.
This is a thin adapter package and behaves like one — it moves when CRAN or an upstream dependency forces it to. Between 2022 and 2024 the feed shows only version bumps, and the 2025 releases are packaging concerns rather than analysis changes. The newly surfaced 2022 entries reinforce rather than change that reading.
Expect the next release to be triggered by a CRAN check failure or an {rbmi} update rather than by new tabulation features.
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 tern.rbmi.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all modeltime.resample alternatives → · See all tern.rbmi 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 tern.rbmi 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 tern.rbmi 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 tern.rbmi alternatives in Analytics are ranked by recent ship velocity. Browse the "tern.rbmi alternatives" section above for the current picks, or visit /alternatives/tern-rbmi for the full list with editorial commentary on each.