← Back to home
Comparison · Analytics

collapse vs modeltime.resample

A side-by-side editorial comparison of collapse and modeltime.resample — release velocity, themes, recent moves, and the top alternatives to consider.

collapse vs modeltime.resample: at a glance

Featurecollapsemodeltime.resample
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdata-transformation, performance, simd, grouped-statisticstime series, cross-validation, tidymodels, compatibility maintenance
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is collapse?

collapse got a JSS paper and a 7x fmean speedup in the same release.

collapse provides fast grouped statistical computing and data transformation for R, built on a C backend with its own grouping, hashing and aggregation primitives. The 2.1.x line is a maintenance and optimization series: SIMD multiple-accumulator work delivering roughly 2x on fsum() and 7x on fmean() for systems without OpenMP, a custom internal unlist() with better attribute preservation, and a steady stream of correctness fixes in collap(), pivot() and roworderv().

Read the full collapse trajectory →

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.

Read the full modeltime.resample trajectory →

collapse vs modeltime.resample: editorial side-by-side

C
collapse
ANALYTICS
0.0

collapse got a JSS paper and a 7x fmean speedup in the same release.

◆ Current state

collapse provides fast grouped statistical computing and data transformation for R, built on a C backend with its own grouping, hashing and aggregation primitives. The 2.1.x line is a maintenance and optimization series: SIMD multiple-accumulator work delivering roughly 2x on fsum() and 7x on fmean() for systems without OpenMP, a custom internal unlist() with better attribute preservation, and a steady stream of correctness fixes in collap(), pivot() and roworderv().

◆ Where it's heading

The package is consolidating institutionally as much as technically. The repository moved to the fastverse organization with multiple people granted access, the Journal of Statistical Software paper landed as the primary citation, and documentation now includes an AI-generated interactive layer. Technically the focus is the hashing and grouping core — the decision to treat -0 and 0 as equal across funique(), group(), fmatch(), fmode() and their derivatives was made in sync with an equivalent change in Rcpp, and accepted a measured 3% cost to get it. The last release with breaking changes sits outside this six-entry window.

◆ Prediction

Expect further targeted performance work on the grouped statistical functions and continued small correctness fixes; the governance move to fastverse suggests contribution volume rather than direction is what the maintainer is managing.

M0.0

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.

Alternatives to collapse and modeltime.resample

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 collapse or modeltime.resample.

See all collapse alternatives → · See all modeltime.resample alternatives →

Recent activity from collapse and modeltime.resample

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2mo agocollapseSIMD accumulators give fmean a 7x speedup without OpenMP
  2. 7mo agocollapseNegative zero now hashes equal to zero across the package
  3. 8mo agocollapsecollap() no longer double-aggregates external weights
  4. 9mo agocollapseCustom unlist() preserves attributes
  5. 11mo agomodeltime.resampletune 2.0 support, deterministic seeding, clearer errors
  6. 11mo agomodeltime.resampleDependency cleanup ahead of the next tune release
  7. 0y agocollapseAssorted bug fixes
  8. 1y agocollapsena_insert gains by-reference mode; gsplit and pivot speed up
  9. 3y agomodeltime.resampleFixes workflows in regression mode
  10. 4y agomodeltime.resampleUpdates for hardhat 1.0.0

Frequently asked questions

What is the difference between collapse and modeltime.resample?

They serve adjacent needs but don't currently overlap on shipped themes. collapse and modeltime.resample 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.

Is collapse better than modeltime.resample?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. collapse and modeltime.resample 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.

What are the best alternatives to collapse?

Top collapse alternatives in Analytics are ranked by recent ship velocity. Browse the "collapse alternatives" section above for the current picks, or visit /alternatives/collapse-r for the full list with editorial commentary on each.

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.