r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of rstantools and simtrial — release velocity, themes, recent moves, and the top alternatives to consider.
The scaffolding layer for Stan-backed R packages, maintained rather than extended.
rstantools generates and maintains the build infrastructure that lets an R package ship Stan models — the inst/stan layout, the auto-generated C++, the Rcpp module loading, and the posterior_* generics downstream packages implement. Its releases are dominated by keeping that scaffolding compiling as Stan, StanHeaders, and rstan move underneath it. Version 2.7.0 continues that pattern, its one user-facing change being an allowance for deprecated syntax in specified versions of specified packages.
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.
rstantools generates and maintains the build infrastructure that lets an R package ship Stan models — the inst/stan layout, the auto-generated C++, the Rcpp module loading, and the posterior_* generics downstream packages implement. Its releases are dominated by keeping that scaffolding compiling as Stan, StanHeaders, and rstan move underneath it. Version 2.7.0 continues that pattern, its one user-facing change being an allowance for deprecated syntax in specified versions of specified packages.
This is a stable dependency in maintenance mode, and the release history reads accordingly: compatibility shims for new rstan and Stan RNG versions, C++ standard bumps, and pkgdown housekeeping. The last substantive API growth was 2.5.0's loo_epred() generic and discrete-data loo_pit(). Contributor churn is visible in recent releases, with several first-time contributors handling infrastructure rather than statistics.
Expect the next releases to continue tracking Stan and rstan breakage as it arrives; nothing in the recent entries points to new generics or a change in the package-generation model.
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.
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.
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.
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 rstantools or simtrial.
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 rstantools alternatives → · See all simtrial alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rstantools 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rstantools 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.
Top rstantools alternatives in Analytics are ranked by recent ship velocity. Browse the "rstantools alternatives" section above for the current picks, or visit /alternatives/rstantools for the full list with editorial commentary on each.
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.