OneArmPhaseTwoStudy
1.0.3CRANPlanning, Conducting, and Analysing Single-Arm Phase II Studies
Record of 1.0.3Compare with 0.1.6LicencesSBOM
Archived on 7 Apr 2021
- CRAN's reason
check problems were not corrected in time. Use of uninitialised memory detected by valgrind
Checks not fixed- Last release
- 1.0.3, 13 Nov 2017
# Needs the pak package.
# install.packages("pak")
# Built from source, so it needs build tools.
pak::pak("cran::OneArmPhaseTwoStudy@1.0.3") - CRAN checks, method
Method
Checks and health
CRAN runs every current package through R CMD check on a set of machines and publishes a result for each one. The health shown on a package page comes from these results alone.
- Problems
- Notes alone never count against a package, but a warning, an error or a failure on any platform is a problem. Open CRAN deadlines are a fact of their own, shown as a clock after the mark, so the mark always says what the checks found.
- Checks only
- Health reflects CRAN's check results and nothing else. Even a package with no tests, no coverage or no recent release can have every platform OK.
- Once a day
- Results are collected once a day from files CRAN publishes. Each platform is one machine set-up, named by its R version, operating system, architecture and compiler, such as r-devel-linux-x86_64-fedora-clang.
- Platforms counted
- The 13 in 3 of 13 is the number of platform rows CRAN published for that package on the day of collection. The set of machines changes over time, so the number is not fixed, and a package missing from a platform counts as neither passing nor failing there.
- Not checkedarchived 7 Apr 2021
- Dependent packages, method
Method
Reverse dependencies
Dependent packages are other packages that list this one under Depends, Imports or LinkingTo in their DESCRIPTION file. Those fields list the packages a package needs to install, so dependents break if this one is archived or broken.
- As declared
- The counts follow the declarations as written, not whether a package uses the other one when it runs.
- Suggests apart
- Packages that list this one only under Suggests install and run without it, and use it for tests, examples or an optional feature. They are counted as Suggested by, never among the dependents, and a package that also lists it under one of the three fields is a dependent and is not counted again.
- Zero
- Zero dependents means no current CRAN package declares a need for this one, though some may suggest it. On 26 Oct 2026, 19,530 of the 25,531 current CRAN packages had no dependent package.
- 0none suggest it
- Advisories, method
Method
Security advisories
Advisories come from the R Consortium advisory database, a community record of security problems in R packages, as OSV publishes it.
- The copy
- The record is read once a day. The data is published under the Apache License 2.0 and is credited on the advisories list.
- Box under the name
- Under the package's name, a box names any advisory that affects the current release, with its fix or that there is none.
- Ranges
- Advisories state ranges, such as from 0.9.12 up to but not including 1.8.8. Each range is checked against every version CRAN has published, using the version rules R itself uses, so a release that came out after the advisory was written is still caught by its range.
- Not the package
- The rating is for the library flaw itself, not for how exposed the R package is, and it is never added up into a figure for the package.
- None known
About
Method, About Method Licence figures come from the License field of each package's DESCRIPTION file, read the way R itself reads it. No licence file is opened.Licences
Purpose of this package is it to plan, monitor and evaluate oncological phase II studies. In general this kind of studies are single-arm trials with planned interim analysis and binary endpoint.
Full description
Purpose of this package is it to plan, monitor and evaluate oncological phase II studies. In general this kind of studies are single-arm trials with planned interim analysis and binary endpoint. To meet the resulting requirements, the package provides functions to calculate and evaluate 'Simon's two-stage designs' and 'so-called' 'subset designs'. If you are unfamiliar with this package a good starting point is to take a closer look at the functions getSolutions() and getSolutionsSub1().The web-based tool (<https://imbi.shinyapps.io/phaseII-app/>) extends the functionality of our R package by means of a proper dealing with over- and underrunning. The R function binom.test of the 'stats' R package and the package 'binom' might be helpful to assess the performance of the corresponding one-stage design as a reference.
- Maintainer
- Johannes Krisam
- Licence
- GPL (>= 2)
- Latest release
- 13 Nov 2017
- First release
- 5 Aug 2014
More details
- Releases
- 5
- Needs R
- >= 3.1.0
- Date
- 2017-11-13
- RoxygenNote
- 6.0.1
Cite
Package
Run in R for the authors' entry:
citation("OneArmPhaseTwoStudy")The package provides a citation file, so citation() returns the authors' own entry.
It points to 10.18637/jss.v081.i08.
R Observatory
For a number measured here: a download total, a coverage figure, an archival date.
Balamuta, J. J. (2026). R Observatory: Metrics for OneArmPhaseTwoStudy version 1.0.3 [Data set]. HJJB, LLC. Data release v2026-10-26. https://doi.org/10.5281/zenodo.21843040
About
From data release v2026-10-26, which the citation names so these numbers can be found later.
Health
CRAN checks only the packages on CRAN, and it archived this one on 7 Apr 2021.
Downloads
Method, Downloads Method Download figures count requests logged by each distribution channel. They are not counts of installs or of users, because each channel publishes its own totals and this site reads them.Downloads
- Total downloads in the last 7 days
- 2It comes from autoCRAN alone.
The total is 2 downloads in the last 7 days. It comes from autoCRAN alone.
Over time
Dependencies
- Needs
- 3
- Dependent packages
- 0
- Suggested by
- 0
Needs (3)
- methods
- Rcpp
- stats
Code
Method, Code Method Code metrics come from reading the released source of each package version. The package is never installed, loaded or run.Code metrics
- Functions
- 158
- Public exports
- 28
- Lines of R code
- 1,552
- Median complexity
- 2
Functions (158)
Size and composition
Lines by kind (5,240)
| Kind | Lines | Share |
|---|---|---|
| R code | 1,552 | 30% |
| Documentation | 1,146 | 22% |
| Compiled code | 2,542 | 49% |
Lines by language
| Language | Lines | Share |
|---|---|---|
| C++ | 1,791 | 34% |
| R | 1,552 | 30% |
| Rd | 1,146 | 22% |
| C | 751 | 14% |
Languages are counted from file extensions.
- Files
- 50
- R functions
- 28
- Compiled functions
- 132
Complexity
- Median
- 2
- Mean
- 3.21
- Highest
- 11
- Median lines per function
- 23
About complexity
Cyclomatic complexity counts the independent paths through a function: 1 is a straight line, higher is harder to test. R functions only.
Call graph figures
- R functions
- 28
- Calls
- 29
- Unconnected
- 2
- Groups
- 3
Growth (5 releases)
Release changes
Tests
Method, Tests Method Test coverage is measured by downloading each CRAN package's current source file, installing its dependencies, building it and running its tests under covr.Test coverage
No coverage run is on record for this package.
- Lines of tests
- 0
- Exports named in tests
- 0%
- Has tests
- No
- Test frameworks
- No tests in this release
- Test lines per line of code
- 0
Documentation
- Exports documented
- 100%
- Arguments documented
- 98.3%
- Return value documented
- 0%
- Help pages with examples
- 86.7%
- Examples run in checks
- 100%
Other documentation
- README
- No
- Release notes file
- No
- Help pages
- 30
- Lines of documentation
- 1,146
People
Method, People Method People on the site are the names packages give them in their DESCRIPTION files: authors from the author list, and the maintainer from the Maintainer field. Spellings of one name become one person only where the rules below allow it, and when in doubt the rules keep people apart.Author and maintainer identity
Maintainer since 1.0.3 (2017), previously Marius Wirths (0.1 to 0.1.6)
Repository
Method, figures by host Method Repository signals are the figures read from the source repository a package links to: stars, forks, issues, commits, releases and the time issues take to close. They are read from GitHub, GitLab and Codeberg.Repository signals
No repository on record
History
Method, History Method Archived is built from CRAN's archive records, its list of check deadlines and Bioconductor's package records. Every figure is counted to 26 Oct 2026, the day the data was read.Packages leaving
- On CRAN
- Archived
- Release
Archived
| Archived | Back | CRAN's reason | Kind |
|---|---|---|---|
| 7 Apr 2021 | not back | check problems were not corrected in time. Use of uninitialised memory detected by valgrind | Checks not fixed |