← Back to home
Comparison · Analytics

gtsummary vs modeltime.ensemble

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

gtsummary vs modeltime.ensemble: at a glance

Featuregtsummarymodeltime.ensemble
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-tables, analysis-results-data, regression-summaries, reproducible-reportingtime series forecasting, ensembles, tidymodels, compatibility maintenance
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is gtsummary?

gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.

gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.

Read the full gtsummary trajectory →

What is modeltime.ensemble?

modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.

modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.

Read the full modeltime.ensemble trajectory →

gtsummary vs modeltime.ensemble: editorial side-by-side

G
gtsummary
ANALYTICS
0.0

gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.

◆ Current state

gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.

◆ Where it's heading

The ARD work is the through-line. Table IDs exist so gather_ard() can return a named list; hierarchical tables gained per-level sorting and targeted filtering; ARD inputs are pre-processed so sorting applies to non-standard shapes. The package is becoming a structured-results engine that happens to render tables, rather than a renderer alone. Alongside that, 2.2.0 restored data pre-processing that 2.0 had removed after the reduced functionality hurt users — a maintainer willing to reverse a major-version decision.

◆ Prediction

Expect the hierarchical and ARD functions, introduced as a preview without a full deprecation cycle, to keep stabilizing toward a settled API rather than new table types appearing.

M0.0

modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.

◆ Current state

modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.

◆ Where it's heading

This is a package whose forecasting capability was settled by 2021 — recursive ensembles, per-series calibration — and whose recent life is dictated entirely by upstream tidymodels churn. New contributors did that compatibility work, including one from the tidymodels side. It now requires tune 2.0.0 and modeltime.resample 0.3.0, pinning it to the current tidymodels generation rather than straddling versions.

◆ Prediction

Expect the next release to follow the next tune or modeltime.resample breaking change rather than to introduce new ensembling methods.

Alternatives to gtsummary and modeltime.ensemble

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 gtsummary or modeltime.ensemble.

See all gtsummary alternatives → · See all modeltime.ensemble alternatives →

Recent activity from gtsummary and modeltime.ensemble

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

  1. 2mo agogtsummaryTheme elements no longer evaluated by default
  2. 8mo agogtsummaryARD strata functions and finer theme control
  3. 11mo agomodeltime.ensembleRealigned for tune 2.0.0 resampling changes
  4. 11mo agomodeltime.ensembleDrops the tidyverse dependency ahead of tune 2.0
  5. 11mo agogtsummaryPer-level hierarchical sorting and labeled stacking
  6. 1y agogtsummaryTable splitting, ID labeling, and add_difference_row
  7. 1y agogtsummaryData pre-processing restored after the 2.0 removal
  8. 1y agogtsummarytbl_merge gains explicit merge columns
  9. 5y agomodeltime.ensemblePer-series calibration IDs and parallel refitting
  10. 5y agomodeltime.ensembleRecursive ensembles for single and panel series

Frequently asked questions

What is the difference between gtsummary and modeltime.ensemble?

They serve adjacent needs but don't currently overlap on shipped themes. gtsummary and modeltime.ensemble 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 gtsummary better than modeltime.ensemble?

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

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

What are the best alternatives to modeltime.ensemble?

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