r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of gsDesign2 and USAboundaries — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.
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.
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.
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.
USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.
For a data package the release cycle is the data vintage, and the 0.3.0 split into a separate data package was designed precisely so those refreshes would not require a code release. That the 2024 update still arrived as two package versions seven years later says the mechanism is being used sparingly. Nothing in the feed shows work on the API itself since us_cities() gained an sf return type and a states argument in 2018.
The next release is most likely another vintage refresh when the census data moves again, rather than new geographies or functions. The split of 0.5.0 and 0.5.1 suggests state boundaries are handled on a separate path from the rest and may lag again.
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 USAboundaries.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all gsDesign2 alternatives → · See all USAboundaries alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
Top USAboundaries alternatives in Analytics are ranked by recent ship velocity. Browse the "USAboundaries alternatives" section above for the current picks, or visit /alternatives/usaboundaries for the full list with editorial commentary on each.