r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of RBesT and simtrial — release velocity, themes, recent moves, and the top alternatives to consider.
RBesT is teaching its Bayesian decision rules to answer two-sided questions.
RBesT builds meta-analytic-predictive priors — the machinery for borrowing historical control data into a new trial — and evaluates the operating characteristics of decisions made with them. The stable line has spent several releases on effective sample size: ESS for normal mixtures via a new `family` argument, boundary corrections when no responses or no non-responses are observed, and stabilised ELIR computations. The 1.9-0 release candidate extends the normal, binomial and Poisson outcome functions to two-sided decisions.
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.
RBesT builds meta-analytic-predictive priors — the machinery for borrowing historical control data into a new trial — and evaluates the operating characteristics of decisions made with them. The stable line has spent several releases on effective sample size: ESS for normal mixtures via a new `family` argument, boundary corrections when no responses or no non-responses are observed, and stabilised ELIR computations. The 1.9-0 release candidate extends the normal, binomial and Poisson outcome functions to two-sided decisions.
Two currents run through the changelog. One is ESS hardening — nearly every release since 1.7-4 fixes another edge case where the ELIR calculation aborted or returned something unstable, which is what happens when a quantity used to justify prior strength to regulators gets scrutinised. The other is Stan and brms integration debt: array syntax updates, a minimum Stan version bump, truncated prior generation for `mixstanvar`, deterministic EM. The RC's contributor list shows a second active maintainer, and the work is broader than any recent stable release.
The release candidate covers all three outcome families and has already absorbed a round of review comments, so the next step is most likely the 1.9-0 CRAN release itself rather than further feature work.
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 RBesT 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 RBesT alternatives → · See all simtrial alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — clinical-trials — within Analytics. RBesT and simtrial are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. RBesT and simtrial are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top RBesT alternatives in Analytics are ranked by recent ship velocity. Browse the "RBesT alternatives" section above for the current picks, or visit /alternatives/rbest 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.