r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
gsDesign2 vs nodbi
A side-by-side editorial comparison of gsDesign2 and nodbi — release velocity, themes, recent moves, and the top alternatives to consider.
gsDesign2 vs nodbi: 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 nodbi?
One document API over six databases, and every release is spent absorbing their JSON engines' churn
nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.
gsDesign2 vs nodbi: 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.
nodbi
0.0ANALYTICS
One document API over six databases, and every release is spent absorbing their JSON engines' churn
◆ Current state
nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.
◆ Where it's heading
Two threads dominate. The first is performance, pursued backend by backend: fast direct NDJSON import moved from DuckDB-only to SQLite and PostgreSQL, query refactors chasing each DuckDB release, and the removal of expensive tree-walking where a cheaper path exists. The second is making results predictable — consistent column types, version checks on the database backend, clearer messages when a Postgres database does not exist yet or when column names contain the dots nodbi reserves for JSON paths.
◆ Prediction
Given that most recent releases are triggered by DuckDB and RSQLite version changes, the next one likely follows the same pattern — adopting a new JSON function or working around a slow one. The duplicate-_id handling added in 0.14.0 suggests NDJSON ingestion edge cases are the current active area.
Alternatives to gsDesign2 and nodbi
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 nodbi.
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 gsDesign2 alternatives → · See all nodbi alternatives →
Recent activity from gsDesign2 and nodbi
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 agonodbijsonb_tree adopted; $in string queries and duplicate _id handling fixed
- 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
- 1y agonodbiDuckDB version parsing and listfields fix
- 1y agonodbidocdb_query reworked for DuckDB 1.3.0
- 1y agonodbiNDJSON writing delegated to DuckDB's internal function
- 1y agonodbiQuery results get consistent column types; fast NDJSON import reaches SQLite and Postgres ⚡
- 1y agonodbiQuery and file-import speedups via newer DuckDB features
Frequently asked questions
What is the difference between gsDesign2 and nodbi?
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 nodbi?
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 nodbi?
Top nodbi alternatives in Analytics are ranked by recent ship velocity. Browse the "nodbi alternatives" section above for the current picks, or visit /alternatives/nodbi for the full list with editorial commentary on each.