tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
gsDesign2 vs Tplyr
A side-by-side editorial comparison of gsDesign2 and Tplyr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:clinical-trialspharmaverser-package
gsDesign2 vs Tplyr: at a glance
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.
What is Tplyr?
Tplyr made clinical summary tables explain where every number came from.
Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.
gsDesign2 vs Tplyr: editorial side-by-side
gsDesign2
3.8ANALYTICS
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.
Tplyr
0.0ANALYTICS
Tplyr made clinical summary tables explain where every number came from.
◆ Current state
Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.
◆ Where it's heading
Post-1.0 work has been about completing the metadata story and filling gaps in layer composition rather than adding table types — metadata for missing subjects, add_anti_join(), missing-subject rows, data limiting, and fixes to nested count layers where an inner value appears under several outer groups. Releases cluster tightly after a major version, then go quiet, and the window ends with a patch issued days after the release it corrects.
◆ Prediction
Further releases will most likely continue closing traceability and nested-layer edge cases rather than introducing new layer types, following the pattern of both post-1.0 feature releases.
Alternatives to gsDesign2 and Tplyr
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 Tplyr.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all gsDesign2 alternatives → · See all Tplyr alternatives →
Recent activity from gsDesign2 and Tplyr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 9d agogsDesign2Harm boundaries land in AHR and NPE group sequential designs ⚡
- 1mo agogsDesign2Conditional power, sequential p-values, and minimal risk weighting
- 5mo agogsDesign2gs_design_ahr() can output spending time
- 8mo agogsDesign2S3 class refactor and futility boundary vignette
- 11mo agogsDesign2h1_spending for WLR power, info_scale across fixed designs
- 1y agogsDesign2WLR design spending default corrected to information fraction
- 2y agoTplyrMissing-subject metadata, add_anti_join(), and nested-layer fixes
- 3y agoTplyrMetadata vignette fix and parenthesis hugging
- 3y agoTplyrDenominator logic fix ahead of CRAN release
- 3y agoTplyrReverse-dependency fix
- 3y agoTplyr1.0.0 introduces the traceability metadata framework ⚡
Frequently asked questions
What is the difference between gsDesign2 and Tplyr?
Both compete on the same themes — clinical-trials, pharmaverse, r-package — within Analytics. 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 Tplyr?
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 Tplyr?
Top Tplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "Tplyr alternatives" section above for the current picks, or visit /alternatives/tplyr for the full list with editorial commentary on each.