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.
A study based on the screened selection design (SSD) is an exploratory phase II randomized trial with two or more arms but without concurrent control. The primary aim of the SSD trial is to pick a desirable treatment arm (e.g., in terms of the median survival time) to recommend to the subsequent randomized phase IIb (with the concurrent control) or phase III. Though The survival endpoint is often encountered in phase II trials, the existing SSD methods cannot deal with the survival endpoint. Furthermore, the existing SSD won’t control the type I error rate. The proposed designs can “partially” control or provide the empirical type I error/false positive rate by an optimal algorithm (implemented by the optimal() function) for each arm. All the design needed components (sample size, operating characteristics) are supported.
Version: | 0.1.1 |
Depends: | survival |
Published: | 2022-04-15 |
DOI: | 10.32614/CRAN.package.frequentistSSD |
Author: | Chia-Wei Hsu [aut, cre], Haitao Pan [aut], Jianrong Wu [aut] |
Maintainer: | Chia-Wei Hsu <Chia-Wei.Hsu at stjude.org> |
License: | GPL-2 |
NeedsCompilation: | no |
CRAN checks: | frequentistSSD results |
Reference manual: | frequentistSSD.pdf |
Package source: | frequentistSSD_0.1.1.tar.gz |
Windows binaries: | r-devel: frequentistSSD_0.1.1.zip, r-release: frequentistSSD_0.1.1.zip, r-oldrel: frequentistSSD_0.1.1.zip |
macOS binaries: | r-release (arm64): frequentistSSD_0.1.1.tgz, r-oldrel (arm64): frequentistSSD_0.1.1.tgz, r-release (x86_64): frequentistSSD_0.1.1.tgz, r-oldrel (x86_64): frequentistSSD_0.1.1.tgz |
Old sources: | frequentistSSD archive |
Please use the canonical form https://CRAN.R-project.org/package=frequentistSSD 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.