monitOS
monitOS relicenses to MIT, the clearest signal in a sparse Novartis release feed.
A side-by-side editorial comparison of filtro and spatstat — 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.
The spatstat umbrella package, now mostly a pointer to the sub-packages doing the work
spatstat is the front package of a family that was split into specialised components — spatstat.geom, spatstat.random, spatstat.model, spatstat.explore, spatstat.univar and spatstat.sparse. Its own release notes reflect that: entries in this window are largely announcements of where the real changes landed, plus documentation and cross-reference maintenance. The codebase it fronts passed 200,000 lines as of 3.5-1.
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.
spatstat is the front package of a family that was split into specialised components — spatstat.geom, spatstat.random, spatstat.model, spatstat.explore, spatstat.univar and spatstat.sparse. Its own release notes reflect that: entries in this window are largely announcements of where the real changes landed, plus documentation and cross-reference maintenance. The codebase it fronts passed 200,000 lines as of 3.5-1.
The split is effectively complete and the umbrella's role has settled into coordination — tracking version dependencies across sub-packages and pointing users to them. The family has kept subdividing over this period, with spatstat.univar joining in 3.1-0. The one substantive user-facing addition here is documentation infrastructure: 3.3-0 added the ability to list the history of changes to a specific function, which is a navigational answer to a codebase now spread across many packages.
Expect this package's notes to continue summarising sub-package activity rather than carrying features of its own, since every release in this window does exactly that. Read spatstat.geom, spatstat.random and spatstat.model for the substance.
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 spatstat.
monitOS relicenses to MIT, the clearest signal in a sparse Novartis release feed.
kernelshap makes permutation SHAP practical past eight features, then fixes the kernel weights it had wrong.
modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.
modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.
shapviz refines its SHAP plots release by release while chasing ggplot2's moving target.
hstats settled into maintenance after its 1.0 restructuring, with model coverage the only thing still growing.
See all filtro alternatives → · See all spatstat 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 spatstat 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 spatstat 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 spatstat alternatives in Analytics are ranked by recent ship velocity. Browse the "spatstat alternatives" section above for the current picks, or visit /alternatives/spatstat-r for the full list with editorial commentary on each.