mrbayes
mrbayes spent 2026 auditing its own Bayesian MR estimators for coding errors.
A side-by-side editorial comparison of modeltime.resample and trias — 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.
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
trias computes and visualizes indicators for the Belgian Tracking Invasive Alien Species project — emergence detection via GAMs, introduction pathway breakdowns following CBD categories, and native range trends. The recent releases are narrow: GAM plots can now be produced without textual annotation when the model cannot be fitted, and apply_decision_rules() no longer supplies a default for a required argument.
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.
trias computes and visualizes indicators for the Belgian Tracking Invasive Alien Species project — emergence detection via GAMs, introduction pathway breakdowns following CBD categories, and native range trends. The recent releases are narrow: GAM plots can now be produced without textual annotation when the model cannot be fitted, and apply_decision_rules() no longer supplies a default for a required argument.
Development runs in small, fast patches concentrated on making the indicator functions survive imperfect real-world input — pathways absent from the data, GAMs that will not converge, checklist files with unexpected columns. A second thread trims the package's own surface in favor of the data it ships, deprecating pathways_cbd() in favor of using the pathwayscbd data frame directly, while get_nubkeys() extends reach into GBIF Backbone taxon key resolution.
Expect continued patch-level hardening of the visualization functions and further reliance on GBIF services for taxon resolution, with no sign of a structural change to the indicator set.
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 trias.
mrbayes spent 2026 auditing its own Bayesian MR estimators for coding errors.
lineup2 ships once every few years, and 2026's release is a logo and a core-count tweak.
stringi has spent two years on build hardening since its Unicode 15.1 reset.
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.
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
See all modeltime.resample alternatives → · See all trias 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 trias 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 trias 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 trias alternatives in Analytics are ranked by recent ship velocity. Browse the "trias alternatives" section above for the current picks, or visit /alternatives/trias-r for the full list with editorial commentary on each.