RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of filtro and scoringutils — release velocity, themes, recent moves, and the top alternatives to consider.
filtro moves to S7 and multiplies its feature-scoring methods in a single release.
filtro supplies feature-selection filter scores for the tidymodels stack. Version 0.2.0 adds five scoring methods — correlation, random forest importance, information gain, ROC AUC and cross tabulation — and moves the package from S3 to S7. It also gains a ranking layer: show_best_score_* and rank_best_score_* helpers for a single score, plus desirability-function helpers for optimising across several scores at once.
scoringutils pushes forecast scoring past univariate outcomes into multivariate and ordinal ones.
scoringutils evaluates probabilistic forecasts in R. Since the 2.0.0 rewrite it is organised around typed forecast objects — quantile, sample, binary, point, nominal — built by as_forecast_<type>() constructors and scored through S3 methods. Version 2.2.0 adds multivariate sample and point types with the variogram score, and 2.1.0 added ordinal forecasts.
filtro supplies feature-selection filter scores for the tidymodels stack. Version 0.2.0 adds five scoring methods — correlation, random forest importance, information gain, ROC AUC and cross tabulation — and moves the package from S3 to S7. It also gains a ranking layer: show_best_score_* and rank_best_score_* helpers for a single score, plus desirability-function helpers for optimising across several scores at once.
The package is being built out on two axes at once — the catalogue of scores, and the machinery for choosing between them. The desirability functions are the more telling half, since they assume users will filter on several criteria rather than one. Adopting S7 while still pre-1.0 suggests the object model is being settled before the API is frozen.
Expect more scoring methods on the same S7 interface and a 1.0 release once the score and ranking APIs stop moving; the ranking helpers' naming is the most likely thing to change first.
scoringutils evaluates probabilistic forecasts in R. Since the 2.0.0 rewrite it is organised around typed forecast objects — quantile, sample, binary, point, nominal — built by as_forecast_<type>() constructors and scored through S3 methods. Version 2.2.0 adds multivariate sample and point types with the variogram score, and 2.1.0 added ordinal forecasts.
The forecast-type system introduced in 2.0.0 is the engine of everything since: each release fits another outcome shape into it rather than reworking the scoring interface. Multivariate support is the largest of those additions because it scores the dependence structure between variables, not just marginal accuracy. Type and constructor names are still being reconciled — forecast_sample_multivariate was renamed to forecast_multivariate_sample with a deprecation window.
Expect further forecast types and metrics slotted into the same constructor pattern, and the deprecated forecast_sample_multivariate alias and is_forecast_sample_multivariate() to be removed once that window closes.
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 filtro or scoringutils.
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 filtro alternatives → · See all scoringutils alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. filtro and scoringutils 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. filtro and scoringutils 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 filtro alternatives in Analytics are ranked by recent ship velocity. Browse the "filtro alternatives" section above for the current picks, or visit /alternatives/filtro-r for the full list with editorial commentary on each.
Top scoringutils alternatives in Analytics are ranked by recent ship velocity. Browse the "scoringutils alternatives" section above for the current picks, or visit /alternatives/scoringutils for the full list with editorial commentary on each.