The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
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[@]metanet.ch.

OptimalGoldstandardDesigns: Design Parameter Optimization for Gold-Standard Non-Inferiority Trials

Methods to calculate optimal design parameters for one- and two-stage three-arm group-sequential gold-standard non-inferiority trial designs with or without binding or nonbinding futility boundaries, as described in Meis et al. (2023) <doi:10.1002/sim.9630>.

Version: 1.0.1
Depends: R (≥ 3.5)
Imports: nloptr, mvtnorm, cli, dplyr, tibble, Rdpack
Suggests: testthat (≥ 3.0.0), here, knitr, rmarkdown, covr, fpCompare, mnormt, future.apply
Published: 2023-09-11
DOI: 10.32614/CRAN.package.OptimalGoldstandardDesigns
Author: Jan Meis ORCID iD [aut, cre]
Maintainer: Jan Meis <meis at imbi.uni-heidelberg.de>
License: GPL (≥ 3)
URL: https://github.com/jan-imbi/OptimalGoldstandardDesigns
NeedsCompilation: no
Citation: OptimalGoldstandardDesigns citation info
Materials: README
CRAN checks: OptimalGoldstandardDesigns results

Documentation:

Reference manual: OptimalGoldstandardDesigns.pdf
Vignettes: Introduction

Downloads:

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

Linking:

Please use the canonical form https://CRAN.R-project.org/package=OptimalGoldstandardDesigns 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.