escalation
0.2.3A Modular Approach to Dose-Finding Clinical Trials
Overview
Methods for working with dose-finding clinical trials. We provide implementations of many dose-finding clinical trial designs, including the continual reassessment method (CRM) by O'Quigley et al. (1990) doi:10.2307/2531628, the toxicity probability interval (TPI) design by Ji et al. (2007) doi:10.1177/1740774507079442, the modified TPI (mTPI) design by Ji et al. (2010) doi:10.1177/1740774510382799, the Bayesian optimal interval design (BOIN) by Liu & Yuan (2015) doi:10.1111/rssc.12089, EffTox by Thall & Cook (2004) doi:10.1111/j.0006-341X.2004.00218.x; the design of Wages & Tait (2015) doi:10.1080/10543406.2014.920873, and the 3+3 described by Korn et al. (1994) doi:10.1002/sim.4780131802. All designs are implemented with a common interface. We also offer optional additional classes to tailor the behaviour of all designs, including avoiding skipping doses, stopping after n patients have been treated at the recommended dose, stopping when a toxicity condition is met, or demanding that n patients are treated before stopping is allowed. By daisy-chaining together these classes using the pipe operator from 'magrittr', it is simple to tailor the behaviour of a dose-finding design so it behaves how the trialist wants. Having provided a flexible interface for specifying designs, we then provide functions to run simulations and calculate dose-paths for future cohorts of patients.
Install
Health
- OK2026-08-0513 OK · 0 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE
- NOTE2026-08-0112 OK · 1 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE
- OK2026-07-2913 OK · 0 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE
- ERROR2026-07-2712 OK · 0 NOTE · 0 WARNING · 1 ERROR · 0 FAILURE
- OK2026-06-0913 OK · 0 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE
Show 3 earlier snapshots
- ERROR2026-06-0712 OK · 0 NOTE · 0 WARNING · 1 ERROR · 0 FAILURE
- OK2026-04-2512 OK · 0 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE
- NOTE2026-03-1011 OK · 3 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE
Documentation
- Examples that run
- 97%
- Documented parameters
- 99%
- Return-value docs
- 93%
- References docs
- 27%
Downloads
Repository
Stars over time
Forks over time
Issues over time
PRs over time
Repository practices
6 development-tooling and community-health practices detected across 5 families in the upstream repository
Checks run against github.com/brockk/escalation on 2026-08-23.
Show all practices
Dependencies
Nothing depends on this yet.
Code & Tests
People & History
9 releases. Pick two to compare their code metrics. R releases are shown for context.
- RR 4.6.0 released · 2026-04-24
- 0.2.3Latest
- RR 4.5.0 released · 2025-04-11
- 0.1.102024-06-27 · diff ↗
- 0.1.92024-05-22 · diff ↗
- RR 4.4.0 released · 2024-04-24
- 0.1.82024-02-23 · diff ↗
- 0.1.52023-05-29 · diff ↗
- RR 4.3.0 released · 2023-04-21
- RR 4.2.0 released · 2022-04-22
- RR 4.1.0 released · 2021-05-18
- 0.1.42020-10-18 · diff ↗
- 0.1.32020-05-13 · diff ↗
- RR 4.0.0 released · 2020-04-24
- 0.1.22020-04-14 · diff ↗
- 0.1.12020-03-08
Show 1 earlier events
- RR 3.6.0 released · 2019-04-26
Package metadata
- First published
- 2020-03-08
- Total releases
- 9 / 6 yrs
- License
- GPL (>= 3) OSI
- Download size
- 4.8 MB
- Installed size
- not tracked yet
- With dependencies
- not tracked yet
Cite
Cite this package
Run in R for the authors' preferred citation:
citation("escalation")This is what citation() produces when a package has no citation file of its own. If it prints something else, use that.
Cite the R Observatory
For a number measured here: a download total, a coverage figure, an archival date.
From data release v2026-08-24, which the citation names so these numbers can be found later. More on citing and the projects behind them.