r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
datapack vs gsDesign2
A side-by-side editorial comparison of datapack and gsDesign2 — release velocity, themes, recent moves, and the top alternatives to consider.
datapack vs gsDesign2: at a glance
What is datapack?
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since
datapack assembles heterogeneous data files and metadata into a single transportable bundle, serialised as an OAI-ORE resource map and BagIt archive, for deposit into repositories like DataONE. Its functional surface settled with the 1.3.x line, which made assembled packages editable rather than write-once. Since then the releases have been sparse and defensive: SHA-256 as the default checksum in 1.4.0, BagIt spec conformance in 1.4.1, and a 2025 patch that states outright it contains no new features.
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.
datapack vs gsDesign2: editorial side-by-side
datapack
0.0ANALYTICS
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since
◆ Current state
datapack assembles heterogeneous data files and metadata into a single transportable bundle, serialised as an OAI-ORE resource map and BagIt archive, for deposit into repositories like DataONE. Its functional surface settled with the 1.3.x line, which made assembled packages editable rather than write-once. Since then the releases have been sparse and defensive: SHA-256 as the default checksum in 1.4.0, BagIt spec conformance in 1.4.1, and a 2025 patch that states outright it contains no new features.
◆ Where it's heading
The arc runs from assembly to correctness of the resulting archive. Later releases keep tightening the metadata the resource map must carry — dc:creator always present, dcterms:modified always updated, the package correctly flagged as modified after any access-policy change — because a bundle whose provenance record is subtly wrong is worse than one that fails outright. The three-year gap between 1.4.1 and 1.4.2, and the latter's CRAN-note content, place this package firmly in preservation.
◆ Prediction
Expect the next release, if any, to be another CRAN-compliance patch rather than functional work. The 1.4.2 note that it contains no new features is the clearest statement in the feed about where this package sits.
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.
Alternatives to datapack and gsDesign2
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 datapack or gsDesign2.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all datapack alternatives → · See all gsDesign2 alternatives →
Recent activity from datapack and gsDesign2
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8d 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
- 10mo agodatapackCRAN documentation and CI cleanup
- 11mo agogsDesign2h1_spending for WLR power, info_scale across fixed designs
- 1y agogsDesign2WLR design spending default corrected to information fraction
- 4y agodatapackBagIt serialisation brought in line with the current spec
- 5y agodatapackSHA-256 becomes the default checksum algorithm
- 6y agodatapackResource map metadata guaranteed; removeRelationships() added
- 8y agodatapackupdateMetadata no longer drops package relationships
- 9y agodatapackAssembled data packages become editable in place ⚡
Frequently asked questions
What is the difference between datapack and gsDesign2?
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 datapack better than gsDesign2?
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 datapack?
Top datapack alternatives in Analytics are ranked by recent ship velocity. Browse the "datapack alternatives" section above for the current picks, or visit /alternatives/datapack for the full list with editorial commentary on each.
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.