← Back to home
Comparison · Analytics

DoseFinding vs simtrial

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

Shared themes:clinical-trials

DoseFinding vs simtrial: at a glance

FeatureDoseFindingsimtrial
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdose-response, mcp-mod, clinical-trials, model-averagingclinical-trials, group-sequential, survival-analysis, simulation
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is DoseFinding?

New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing

DoseFinding implements MCP-Mod and related dose-response methodology for clinical trial design and analysis. In 2024 it changed hands — Marius Thomas took over as maintainer, Novartis was recorded as copyright holder and funder, and the package moved to the openpharma GitHub organisation with roxygen documentation and a proper NEWS file. The two releases since have added substantive methodology: model averaging for dose-response fitting in 1.3-1, and conditional and predictive power for interim analyses in 1.4-1.

Read the full DoseFinding 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 →

DoseFinding vs simtrial: editorial side-by-side

D
DoseFinding
ANALYTICS
0.0

New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing

◆ Current state

DoseFinding implements MCP-Mod and related dose-response methodology for clinical trial design and analysis. In 2024 it changed hands — Marius Thomas took over as maintainer, Novartis was recorded as copyright holder and funder, and the package moved to the openpharma GitHub organisation with roxygen documentation and a proper NEWS file. The two releases since have added substantive methodology: model averaging for dose-response fitting in 1.3-1, and conditional and predictive power for interim analyses in 1.4-1.

◆ Where it's heading

The pattern before the handover was maintenance — R-devel compliance, a bug fix, a link. After it, each release carries a named methodological addition with an acknowledged contributor, plus documentation to match: a longitudinal analysis vignette shipped alongside the interim power work. Housekeeping continues underneath, mostly clearing deprecated ggplot2 interfaces, aes_string in one release and qplot in the next.

◆ Prediction

Given the last two releases each added one method with a supporting vignette, expect the next to follow the same shape. Both additions so far extend the package beyond fixed dose-response fitting, so adaptive and interim methodology is the more likely direction.

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 DoseFinding 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 DoseFinding or simtrial.

See all DoseFinding alternatives → · See all simtrial alternatives →

Recent activity from DoseFinding and simtrial

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

  1. 8mo agosimtrialOne-sided efficacy bound and stratified cut date corrected
  2. 11mo agosimtrialsim_gs_n moved to data.table; stratified design example added
  3. 1y agoDoseFindingConditional and predictive power for interim analyses
  4. 1y agosimtrial1.0.0 settles the wlr interface and documents both simulation paths
  5. 1y agoDoseFindingModel averaging arrives for dose-response fitting
  6. 1y agosimtrialMilestone Z-score denominator corrected; parallel sim_fixed_n arrives
  7. 1y agoDoseFindingPackage moves to openpharma under new maintainership
  8. 2y agosimtrialChecks pass without Suggests dependencies
  9. 2y agosimtrialRMST and milestone tests, plus a user-definable cut and test framework
  10. 2y agoDoseFindingCompliance update for R-devel
  11. 3y agoDoseFindingpowMCTBinCount bug fix

Frequently asked questions

What is the difference between DoseFinding and simtrial?

Both compete on the same themes — clinical-trials — within Analytics. DoseFinding 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 DoseFinding better than simtrial?

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

Top DoseFinding alternatives in Analytics are ranked by recent ship velocity. Browse the "DoseFinding alternatives" section above for the current picks, or visit /alternatives/dosefinding 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.