← Back to home
Comparison · Analytics

rtflite vs simtrial

A side-by-side editorial comparison of rtflite and simtrial — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:pharmaverse

rtflite vs simtrial: at a glance

Featurertflitesimtrial
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-reporting, python, document-conversion, rtfclinical-trials, group-sequential, survival-analysis, simulation
Last editorial update1h ago46m ago
WebsiteVisit →Visit →

What is rtflite?

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.

Read the full rtflite trajectory →

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.

Read the full simtrial trajectory →

rtflite vs simtrial: editorial side-by-side

R
rtflite
ANALYTICS
0.0

rtflite stopped being an RTF writer and became the conversion layer for clinical table output.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

S
simtrial
ANALYTICS
0.0

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.

Alternatives to rtflite and simtrial

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.

See all rtflite alternatives → · See all simtrial alternatives →

Recent activity from rtflite and simtrial

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agortfliteMulti-section body typing tightened; pandas dropped from dev deps
  2. 7mo agortfliteAPI reference renders Pydantic field metadata
  3. 7mo agortfliteDocumentation site migrated to Zensical
  4. 7mo agortfliteSnapshot tests moved to pytest-r-snapshot
  5. 7mo agortfliteHTML and PDF export complete the output matrix
  6. 7mo agortfliteLibreOffice conversion becomes an injectable converter object
  7. 8mo agosimtrialOne-sided efficacy bound and stratified cut date corrected
  8. 11mo agosimtrialsim_gs_n moved to data.table; stratified design example added
  9. 1y agosimtrial1.0.0 settles the wlr interface and documents both simulation paths
  10. 1y agosimtrialMilestone Z-score denominator corrected; parallel sim_fixed_n arrives
  11. 2y agosimtrialChecks pass without Suggests dependencies
  12. 2y agosimtrialRMST and milestone tests, plus a user-definable cut and test framework

Frequently asked questions

What is the difference between rtflite and simtrial?

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.

Is rtflite better than simtrial?

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.

What are the best alternatives to rtflite?

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.

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.