monitOS
monitOS relicenses to MIT, the clearest signal in a sparse Novartis release feed.
Comparison · Analytics
modeltime.resample vs spatstat.geom
A side-by-side editorial comparison of modeltime.resample and spatstat.geom — release velocity, themes, recent moves, and the top alternatives to consider.
modeltime.resample vs spatstat.geom: at a glance
| Feature | modeltime.resample | spatstat.geom |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | time series, cross-validation, tidymodels, compatibility maintenance | spatial-statistics, computational-geometry, r-package, three-dimensional |
| Last editorial update | 45m ago | 1h ago |
| Website | Visit → | Visit → |
What is modeltime.resample?
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.
What is spatstat.geom?
The geometry layer under spatstat, steadily absorbing 3D patterns and missing-data semantics
spatstat.geom holds the spatial data structures and geometric operations the rest of the spatstat family builds on — windows, tessellations, images, point patterns and the operations that move between them. Recent releases split their attention between extending those structures to three dimensions and hardening the discretisation code where polygonal geometry meets a pixel grid. 3.8-2 adds more capabilities for three-dimensional point patterns.
modeltime.resample vs spatstat.geom: editorial side-by-side
modeltime.resample
0.0ANALYTICS
modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect the next release to track the next tidymodels breaking change, with any new work continuing on error reporting rather than resampling strategies.
spatstat.geom
2.5ANALYTICS
The geometry layer under spatstat, steadily absorbing 3D patterns and missing-data semantics
◆ Current state
spatstat.geom holds the spatial data structures and geometric operations the rest of the spatstat family builds on — windows, tessellations, images, point patterns and the operations that move between them. Recent releases split their attention between extending those structures to three dimensions and hardening the discretisation code where polygonal geometry meets a pixel grid. 3.8-2 adds more capabilities for three-dimensional point patterns.
◆ Where it's heading
Two threads run through this window. The first is a family-wide push into 3D that originated in the simulation package and has now reached the geometry layer. The second is a slower semantic change: 3.5-0 introduced missing or unavailable (NA) spatial objects, and 3.6-0 followed with more facilities for handling them, meaning an absent window or image became a representable value rather than an error. Around both, the plotting and discretisation code accretes steadily — nonlinear colour maps, plot backgrounds, transparency control, signed distance transforms, and repeated attention to boundary pixels.
◆ Prediction
Expect the 3D surface here to keep filling in behind the simulation package rather than leading it, given that 3.8-2 follows the 3D simulation release by two months. The entries give no indication that the NA work is finished, since it has already spanned two releases.
Alternatives to modeltime.resample and spatstat.geom
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 spatstat.geom.
kernelshap
kernelshap makes permutation SHAP practical past eight features, then fixes the kernel weights it had wrong.
filtro
filtro moves to S7 and multiplies its feature-scoring methods in a single release.
modeltime.ensemble
modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.
shapviz
shapviz refines its SHAP plots release by release while chasing ggplot2's moving target.
hstats
hstats settled into maintenance after its 1.0 restructuring, with model coverage the only thing still growing.
See all modeltime.resample alternatives → · See all spatstat.geom alternatives →
Recent activity from modeltime.resample and spatstat.geom
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20d agospatstat.geomMore three-dimensional point pattern capabilities
- 2mo agospatstat.geomBetter boundary pixel handling when discretising windows
- 6mo agospatstat.geomAnalytic level sets and signed distance transforms
- 10mo agospatstat.geomNA object handling extended; clickpoly gains grid snapping
- 11mo agomodeltime.resampletune 2.0 support, deterministic seeding, clearer errors
- 11mo agomodeltime.resampleDependency cleanup ahead of the next tune release
- 1y agospatstat.geomNA spatial objects, hole removal and connected components
- 1y agospatstat.geomNonlinear colour and symbol maps; half-open quadrat tiles
- 3y agomodeltime.resampleFixes workflows in regression mode
- 4y agomodeltime.resampleUpdates for hardhat 1.0.0
Frequently asked questions
What is the difference between modeltime.resample and spatstat.geom?
They serve adjacent needs but don't currently overlap on shipped themes. spatstat.geom is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is modeltime.resample better than spatstat.geom?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. spatstat.geom is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to modeltime.resample?
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.
What are the best alternatives to spatstat.geom?
Top spatstat.geom alternatives in Analytics are ranked by recent ship velocity. Browse the "spatstat.geom alternatives" section above for the current picks, or visit /alternatives/spatstat-geom for the full list with editorial commentary on each.