The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.

dtpcrm: Dose Transition Pathways for Continual Reassessment Method

Provides the dose transition pathways (DTP) to project in advance the doses recommended by a model-based design for subsequent patients (stay, escalate, deescalate or stop early) using all the accumulated toxicity information; See Yap et al (2017) <doi:10.1158/1078-0432.CCR-17-0582>. DTP can be used as a design and an operational tool and can be displayed as a table or flow diagram. The 'dtpcrm' package also provides the modified continual reassessment method (CRM) and time-to-event CRM (TITE-CRM) with added practical considerations to allow stopping early when there is sufficient evidence that the lowest dose is too toxic and/or there is a sufficient number of patients dosed at the maximum tolerated dose.

Version: 0.1.1
Imports: diagram, dfcrm
Suggests: knitr, rmarkdown, testthat
Published: 2019-08-20
Author: Christina Yap [aut, cre], Daniel Slade [aut], Kristian Brock [aut], Yi Pan [aut]
Maintainer: Christina Yap <yapchristina17 at gmail.com>
License: GPL-2 | GPL-3 [expanded from: GPL (≥ 2)]
NeedsCompilation: no
CRAN checks: dtpcrm results

Documentation:

Reference manual: dtpcrm.pdf
Vignettes: dtpcrm: Dose Transition Pathways with Continual Reassessment Method

Downloads:

Package source: dtpcrm_0.1.1.tar.gz
Windows binaries: r-devel: dtpcrm_0.1.1.zip, r-release: dtpcrm_0.1.1.zip, r-oldrel: dtpcrm_0.1.1.zip
macOS binaries: r-release (arm64): dtpcrm_0.1.1.tgz, r-oldrel (arm64): dtpcrm_0.1.1.tgz, r-release (x86_64): dtpcrm_0.1.1.tgz, r-oldrel (x86_64): dtpcrm_0.1.1.tgz
Old sources: dtpcrm archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=dtpcrm to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.