r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
simtrial vs sofa
A side-by-side editorial comparison of simtrial and sofa — release velocity, themes, recent moves, and the top alternatives to consider.
simtrial vs sofa: at a glance
What is simtrial?
A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers
simtrial simulates time-to-event clinical trials and applies the tests used to analyse them — logrank, weighted logrank, MaxCombo, RMST, milestone. The 0.4.0 release turned it from a fixed-sample simulator into a group sequential one and standardised every test behind a common output contract, and the releases since have been about making that machinery correct and fast enough to run at scale. Version 1.0.0 arrived in June 2025 with the API settled and three vignettes explaining both the one-call and build-it-yourself paths.
What is sofa?
A CouchDB client for R whose recent work is all test infrastructure, not new routes.
sofa wraps the CouchDB HTTP API for R — database and document CRUD, Mango queries and indexes, design documents, replication, and attachments, organized around a Cushion connection object. Feature development effectively stopped after 0.4.0 brought CouchDB v3 compatibility in 2020. The two 2026 releases are a testing and packaging overhaul: 0.4.1 rebuilt the suite around a crul-mocked fake CouchDB so tests no longer need Cloudant or a local Docker instance, reaching 100% coverage, and 0.4.2 cleared CRAN check notes.
simtrial vs sofa: editorial side-by-side
simtrial
0.0ANALYTICS
A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers
◆ Current state
simtrial simulates time-to-event clinical trials and applies the tests used to analyse them — logrank, weighted logrank, MaxCombo, RMST, milestone. The 0.4.0 release turned it from a fixed-sample simulator into a group sequential one and standardised every test behind a common output contract, and the releases since have been about making that machinery correct and fast enough to run at scale. Version 1.0.0 arrived in June 2025 with the API settled and three vignettes explaining both the one-call and build-it-yourself paths.
◆ Where it's heading
Post-1.0 the work is almost entirely statistical correctness and speed, and it is concentrated in sim_gs_n(): one-sided efficacy bounds, stratified targeted-event cut dates, a helper that derives cuttings straight from the design object. Performance moves in one direction throughout — dplyr replaced by data.table, foreach combination replaced by manual assembly, parallelisation added to sim_fixed_n() — because simulation-based operating characteristics are only useful if you can afford enough replications.
◆ Prediction
The recent fixes cluster on stratified and group sequential paths, so the next release most likely continues there rather than adding a new test type. The cut_from_design() helper suggests tighter coupling to gsDesign2 design objects is the direction of travel.
sofa
2.5ANALYTICS
A CouchDB client for R whose recent work is all test infrastructure, not new routes.
◆ Current state
sofa wraps the CouchDB HTTP API for R — database and document CRUD, Mango queries and indexes, design documents, replication, and attachments, organized around a Cushion connection object. Feature development effectively stopped after 0.4.0 brought CouchDB v3 compatibility in 2020. The two 2026 releases are a testing and packaging overhaul: 0.4.1 rebuilt the suite around a crul-mocked fake CouchDB so tests no longer need Cloudant or a local Docker instance, reaching 100% coverage, and 0.4.2 cleared CRAN check notes.
◆ Where it's heading
This is a rOpenSci package being brought back to a maintainable state rather than extended. The 0.4.1 decision to mock the server is the consequential one — it decouples CI from a live CouchDB, which is what made the cross-platform GitHub Actions workflow and full coverage possible at all. Two genuine bugs surfaced in that process, in db_replicate() URL construction against non-Cloudant servers and db_alldocs(disk=) not returning the documented file path, suggesting the untested paths had drifted.
◆ Prediction
With the test harness now self-contained, the next plausible move is catching up on CouchDB routes added since v3 rather than further infrastructure work, though nothing in these entries commits to it.
Alternatives to simtrial and sofa
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 simtrial or sofa.
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 simtrial alternatives → · See all sofa alternatives →
Recent activity from simtrial and sofa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21d agosofaCRAN check notes and metadata corrections
- 2mo agosofaTests moved to a mocked CouchDB, coverage to 100%
- 8mo agosimtrialOne-sided efficacy bound and stratified cut date corrected
- 11mo agosimtrialsim_gs_n moved to data.table; stratified design example added
- 1y agosimtrial1.0.0 settles the wlr interface and documents both simulation paths
- 1y agosimtrialMilestone Z-score denominator corrected; parallel sim_fixed_n arrives
- 2y agosimtrialChecks pass without Suggests dependencies
- 2y agosimtrialRMST and milestone tests, plus a user-definable cut and test framework ⚡
- 6y agosofaCouchDB v3 support, doc_upsert() and bulk get
- 8y agosofaMango index management and batched design search
- 9y agosofasofa v0.2.0
Frequently asked questions
What is the difference between simtrial and sofa?
They serve adjacent needs but don't currently overlap on shipped themes. sofa is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 simtrial better than sofa?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. sofa is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 simtrial?
Top simtrial alternatives in Analytics are ranked by recent ship velocity. Browse the "simtrial alternatives" section above for the current picks, or visit /alternatives/simtrial for the full list with editorial commentary on each.
What are the best alternatives to sofa?
Top sofa alternatives in Analytics are ranked by recent ship velocity. Browse the "sofa alternatives" section above for the current picks, or visit /alternatives/sofa for the full list with editorial commentary on each.