RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of filtro and prism — 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.
prism rebuilds on Oregon State's new API and starts the move to cloud-optimised GeoTIFF.
prism downloads and handles PRISM climate data in R. Version 0.3.0 rewrites the package against the API Oregon State introduced in September 2025, arriving after a gap the maintainer apologises for. Normals now download as cloud-optimised GeoTIFF rather than .bil, so helper functions such as pd_plot_slice() and pd_image() do not work with them. Archives mixing old and new API data trigger a warning and a recommendation to start fresh.
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.
prism downloads and handles PRISM climate data in R. Version 0.3.0 rewrites the package against the API Oregon State introduced in September 2025, arriving after a gap the maintainer apologises for. Normals now download as cloud-optimised GeoTIFF rather than .bil, so helper functions such as pd_plot_slice() and pd_image() do not work with them. Archives mixing old and new API data trigger a warning and a recommendation to start fresh.
The package is mid-migration on two axes at once: the API endpoint, which is done, and the file format, where only normals have moved to COG while everything else still fetches .bil. The stated plan is to take the whole package to COG. Until that lands, capability is split — data downloads fine, but the plotting and slicing helpers only cover the old format.
The next substantive release should extend COG downloads beyond normals and restore the helper functions against that format, closing the gap this release opened.
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 prism.
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 prism alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r package — within Analytics. filtro and prism 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 prism 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 prism alternatives in Analytics are ranked by recent ship velocity. Browse the "prism alternatives" section above for the current picks, or visit /alternatives/prism-r for the full list with editorial commentary on each.