← Back to home
Comparison · Analytics

simtrial vs typst-gather

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

simtrial vs typst-gather: at a glance

Featuresimtrialtypst-gather
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-trials, group-sequential, survival-analysis, simulationtypst, hermetic-builds, rust, cli-tooling
Last editorial update49m ago1h ago
WebsiteVisit →Visit →

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 →

What is typst-gather?

Extracted from Quarto's CLI, typst-gather learned to explain a dependency tree before fetching it.

typst-gather collects Typst packages into a local cache so documents build offline and hermetically. It was extracted from quarto-cli and reached CRAN-equivalent shape in three releases over a single day, then added an `analyze` subcommand that walks `@Preview` and `@Local` imports — following transitive dependencies of local packages — and prints structured JSON without downloading or copying anything.

Read the full typst-gather trajectory →

simtrial vs typst-gather: editorial side-by-side

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.

T
typst-gather
ANALYTICS
0.0

Extracted from Quarto's CLI, typst-gather learned to explain a dependency tree before fetching it.

◆ Current state

typst-gather collects Typst packages into a local cache so documents build offline and hermetically. It was extracted from quarto-cli and reached CRAN-equivalent shape in three releases over a single day, then added an `analyze` subcommand that walks `@Preview` and `@Local` imports — following transitive dependencies of local packages — and prints structured JSON without downloading or copying anything.

◆ Where it's heading

The 0.2.0 restructuring is the tell: subcommands with backwards compatibility, config readable from stdin, and every diagnostic message moved to stderr so stdout carries nothing but JSON. Those are the conventions of a tool meant to be called by another program, not typed by a person. Given its origin inside Quarto's toolchain, the plausible consumer is a build system that needs to know a document's package requirements before deciding what to fetch.

◆ Prediction

The analyze path currently reports imports; the natural extension visible from here is acting on that report — lockfile output or verification that a cache satisfies a document's dependency set — though the entries do not commit to either.

Alternatives to simtrial and typst-gather

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 typst-gather.

See all simtrial alternatives → · See all typst-gather alternatives →

Recent activity from simtrial and typst-gather

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

  1. 5mo agotypst-gatheranalyze subcommand reports the import graph as JSON
  2. 5mo agotypst-gatherWindows path escaping fix and README expansion
  3. 5mo agotypst-gatherSplit out of quarto-cli as a standalone package gatherer
  4. 8mo agosimtrialOne-sided efficacy bound and stratified cut date corrected
  5. 11mo agosimtrialsim_gs_n moved to data.table; stratified design example added
  6. 1y agosimtrial1.0.0 settles the wlr interface and documents both simulation paths
  7. 1y agosimtrialMilestone Z-score denominator corrected; parallel sim_fixed_n arrives
  8. 2y agosimtrialChecks pass without Suggests dependencies
  9. 2y agosimtrialRMST and milestone tests, plus a user-definable cut and test framework

Frequently asked questions

What is the difference between simtrial and typst-gather?

They serve adjacent needs but don't currently overlap on shipped themes. simtrial and typst-gather 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 simtrial better than typst-gather?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. simtrial and typst-gather 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 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 typst-gather?

Top typst-gather alternatives in Analytics are ranked by recent ship velocity. Browse the "typst-gather alternatives" section above for the current picks, or visit /alternatives/typst-gather for the full list with editorial commentary on each.