← Back to home
Comparison · Analytics

gsDesign2 vs tidymodels

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

gsDesign2 vs tidymodels: at a glance

FeaturegsDesign2tidymodels
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesclinical-trials, group-sequential, biostatistics, pharmaversetidymodels, meta-package, dependency-management, namespace-conflicts
Last editorial update2h ago46m ago
WebsiteVisit →Visit →

What is gsDesign2?

Group sequential design tooling that now monitors for harm, not just efficacy and futility.

gsDesign2 is the Merck-authored R package for group sequential clinical trial design under non-proportional hazards, and it has spent the last two years filling in the statistical surface its predecessor gsDesign established. Recent releases added conditional power (gs_cp, gs_cp_npe), sequential p-values, risk-difference designs with minimal risk weighting, and boundary updates from blinded interim estimates. Version 1.2.0 adds harm boundaries across the AHR and NPE design and power functions, wired through every summary and table export path.

Read the full gsDesign2 trajectory →

What is tidymodels?

The meta-package ships almost nothing, which is exactly what a version-pinning shim should do

The tidymodels package is a loader and version pin for the modeling framework's core set rather than a place where features live. Its entire changelog consists of updated dependency versions, adjustments to how tidymodels_prefer() resolves name conflicts against other packages, and the occasional addition of a package to the core set — workflowsets in 0.1.3, tailor in 1.4.0. The most recent releases moved the package's own code from the magrittr pipe to R's base pipe and patched a bug where some attached packages were omitted.

Read the full tidymodels trajectory →

gsDesign2 vs tidymodels: editorial side-by-side

G
gsDesign2
ANALYTICS
3.8

Group sequential design tooling that now monitors for harm, not just efficacy and futility.

◆ Current state

gsDesign2 is the Merck-authored R package for group sequential clinical trial design under non-proportional hazards, and it has spent the last two years filling in the statistical surface its predecessor gsDesign established. Recent releases added conditional power (gs_cp, gs_cp_npe), sequential p-values, risk-difference designs with minimal risk weighting, and boundary updates from blinded interim estimates. Version 1.2.0 adds harm boundaries across the AHR and NPE design and power functions, wired through every summary and table export path.

◆ Where it's heading

The package is converging on parity with gsDesign while extending past it — each release either closes a gap against the older package or adds a boundary type gsDesign never had. A visible second track is output plumbing: every new statistical feature now arrives already threaded through summary(), gs_bound_summary(), as_gt(), and as_rtf(), which is what regulatory submission work actually consumes. Performance work is steady but secondary, with gs_design_ahr() roughly 2x faster in 1.1.9.

◆ Prediction

Expect the harm boundary work to propagate into the WLR and risk-difference design families, which are the two design branches 1.2.0 left untouched, along with a vignette bridging harm boundaries to the remaining gsDesign test types.

T
tidymodels
ANALYTICS
0.0

The meta-package ships almost nothing, which is exactly what a version-pinning shim should do

◆ Current state

The tidymodels package is a loader and version pin for the modeling framework's core set rather than a place where features live. Its entire changelog consists of updated dependency versions, adjustments to how tidymodels_prefer() resolves name conflicts against other packages, and the occasional addition of a package to the core set — workflowsets in 0.1.3, tailor in 1.4.0. The most recent releases moved the package's own code from the magrittr pipe to R's base pipe and patched a bug where some attached packages were omitted.

◆ Where it's heading

Release cadence tracks the ecosystem rather than any roadmap of its own: a version bump when member packages release, a tidymodels_prefer() rule when a new conflict appears — DALEX::explains() over dplyr::explains(), recipes::update() over other update() methods. Additions to the core set are the only structurally interesting events, and there have been two in seven releases. Everything else is plumbing that exists so a single library() call attaches a consistent set of versions.

◆ Prediction

The next release will most likely be another version-set update, with any new core package the only thing worth noting. Feature news for this framework will keep arriving in the member packages, not here.

Alternatives to gsDesign2 and tidymodels

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 gsDesign2 or tidymodels.

See all gsDesign2 alternatives → · See all tidymodels alternatives →

Recent activity from gsDesign2 and tidymodels

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

  1. 8d agogsDesign2Harm boundaries land in AHR and NPE group sequential designs
  2. 1mo agogsDesign2Conditional power, sequential p-values, and minimal risk weighting
  3. 5mo agogsDesign2gs_design_ahr() can output spending time
  4. 8mo agogsDesign2S3 class refactor and futility boundary vignette
  5. 11mo agogsDesign2h1_spending for WLR power, info_scale across fixed designs
  6. 11mo agotidymodelsFix for packages omitted from attachment
  7. 11mo agotidymodelstailor joins the core set; base pipe replaces magrittr
  8. 1y agogsDesign2WLR design spending default corrected to information fraction
  9. 1y agotidymodelsConflict preferences added for DALEX and recipes
  10. 3y agotidymodelsConflict preferences and pinned versions refreshed
  11. 4y agotidymodelsVersion refresh and testthat 3e migration
  12. 4y agotidymodelsRotating startup messages and an analysis template

Frequently asked questions

What is the difference between gsDesign2 and tidymodels?

They serve adjacent needs but don't currently overlap on shipped themes. gsDesign2 is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 gsDesign2 better than tidymodels?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gsDesign2 is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 gsDesign2?

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

What are the best alternatives to tidymodels?

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