r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of rtflite and simtrial — release velocity, themes, recent moves, and the top alternatives to consider.
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.
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.
rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.
Every format addition routes through the same LibreOffice converter rather than a per-format implementation, and 2.4.0's breaking change made that converter an injectable object you can configure and reuse. That is the shape of a package expecting to run inside a pipeline that produces hundreds of tables, not one that converts a document at a time. The recent quiet — snapshot tests moved onto `pytest-r-snapshot`, docs migrated, pandas and pyarrow dropped from dev dependencies — reads as work to stay dependency-light while the surface stabilizes.
With the export matrix filled in and three consecutive infrastructure-only releases, the next substantive change is most likely on the input side — table construction and pagination — since `page_by` and `subline_by` are the only feature area still generating bug reports in these notes.
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 rtflite 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 rtflite alternatives → · See all simtrial alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — pharmaverse — within Analytics. rtflite 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. rtflite 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 rtflite alternatives in Analytics are ranked by recent ship velocity. Browse the "rtflite alternatives" section above for the current picks, or visit /alternatives/rtflite 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.