osDesign
Design, Planning and Analysis of Observational Studies
v1.8
·
Nov 15, 2020
·
GPL (>= 3)
Description
A suite of functions for the design of case-control and two-phase studies, and the analysis of data that arise from them. Functions in this packages provides Monte Carlo based evaluation of operating characteristics such as powers for estimators of the components of a logistic regression model. For additional detail see: Haneuse S, Saegusa T and Lumley T (2011)<doi:10.18637/jss.v043.i11>.
Downloads
333
Last 30 days
11648th
917
Last 90 days
3.7K
Last year
Trend: +14.4% (30d vs prior 30d)
CRAN Check Status
14
NOTE
Show all 14 flavors
| Flavor | Status |
|---|---|
| r-devel-linux-x86_64-debian-clang | NOTE |
| r-devel-linux-x86_64-debian-gcc | NOTE |
| r-devel-linux-x86_64-fedora-clang | NOTE |
| r-devel-linux-x86_64-fedora-gcc | NOTE |
| r-devel-macos-arm64 | NOTE |
| r-devel-windows-x86_64 | NOTE |
| r-oldrel-macos-arm64 | NOTE |
| r-oldrel-macos-x86_64 | NOTE |
| r-oldrel-windows-x86_64 | NOTE |
| r-patched-linux-x86_64 | NOTE |
| r-release-linux-x86_64 | NOTE |
| r-release-macos-arm64 | NOTE |
| r-release-macos-x86_64 | NOTE |
| r-release-windows-x86_64 | NOTE |
Check details (16 non-OK)
NOTE
r-devel-linux-x86_64-debian-clang
CRAN incoming feasibility
Maintainer: ‘Sebastien Haneuse <shaneuse@hsph.harvard.edu>’
No Authors@R field in DESCRIPTION.
Please add one, modifying
Authors@R: c(person(given = "Sebastien",
family = "Haneuse",
role = c("aut", "cre"),
email = "shaneuse@hsph.harvard.edu"),
person(given = "Takumi",
family = "Saegusa",
role = "aut"),
person(given = "Nilanjan",
family = "Chaterjee",
role = "aut"),
person(given = "Norman",
family = "Breslow",
role = "aut"))
as necessary.
Package CITATION file contains call(s) to old-style personList() or
as.personList(). Please use c() on person objects instead.
Package CITATION file contains call(s) to old-style citEntry(). Please
use bibentry() instead.
NOTE
r-devel-linux-x86_64-debian-clang
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:78: Lost braces; missing escapes or markup?
78 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each
...[truncated]...
ed coding convention.
| ^
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-devel-linux-x86_64-debian-gcc
CRAN incoming feasibility
Maintainer: ‘Sebastien Haneuse <shaneuse@hsph.harvard.edu>’
No Authors@R field in DESCRIPTION.
Please add one, modifying
Authors@R: c(person(given = "Sebastien",
family = "Haneuse",
role = c("aut", "cre"),
email = "shaneuse@hsph.harvard.edu"),
person(given = "Takumi",
family = "Saegusa",
role = "aut"),
person(given = "Nilanjan",
family = "Chaterjee",
role = "aut"),
person(given = "Norman",
family = "Breslow",
role = "aut"))
as necessary.
Package CITATION file contains call(s) to old-style personList() or
as.personList(). Please use c() on person objects instead.
Package CITATION file contains call(s) to old-style citEntry(). Please
use bibentry() instead.
NOTE
r-devel-linux-x86_64-debian-gcc
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:78: Lost braces; missing escapes or markup?
78 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each
...[truncated]...
ed coding convention.
| ^
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-devel-linux-x86_64-fedora-clang
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:78: Lost braces; missing escapes or markup?
78 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each
...[truncated]...
ed coding convention.
| ^
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-devel-linux-x86_64-fedora-gcc
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:78: Lost braces; missing escapes or markup?
78 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each
...[truncated]...
ed coding convention.
| ^
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-devel-macos-arm64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:78: Lost braces; missing escapes or markup?
78 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each
...[truncated]...
ed coding convention.
| ^
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-devel-windows-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:78: Lost braces; missing escapes or markup?
78 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each
...[truncated]...
ed coding convention.
| ^
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-oldrel-macos-arm64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:70: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:71: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:72: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:73: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:74: Lo
...[truncated]...
ze; meant \describe ?
checkRd: (-1) tpsSim.Rd:100: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:101: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:102: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:103: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-oldrel-macos-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:70: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:71: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:72: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:73: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:74: Lo
...[truncated]...
ze; meant \describe ?
checkRd: (-1) tpsSim.Rd:100: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:101: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:102: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:103: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-oldrel-windows-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:70: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:71: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:72: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:73: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:74: Lo
...[truncated]...
ze; meant \describe ?
checkRd: (-1) tpsSim.Rd:100: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:101: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:102: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:103: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-patched-linux-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:78: Lost braces; missing escapes or markup?
78 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each
...[truncated]...
ed coding convention.
| ^
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-release-linux-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:78: Lost braces; missing escapes or markup?
78 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each
...[truncated]...
ed coding convention.
| ^
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-release-macos-arm64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:70: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:71: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:72: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:73: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:74: Lo
...[truncated]...
ze; meant \describe ?
checkRd: (-1) tpsSim.Rd:100: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:101: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:102: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:103: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-release-macos-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:70: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:71: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:72: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:73: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:74: Lo
...[truncated]...
ze; meant \describe ?
checkRd: (-1) tpsSim.Rd:100: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:101: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:102: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:103: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
NOTE
r-release-windows-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
checkRd: (-1) ccSim.Rd:70: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:71: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:72: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:73: Lost braces in \itemize; meant \describe ?
checkRd: (-1) ccSim.Rd:74: Lo
...[truncated]...
ze; meant \describe ?
checkRd: (-1) tpsSim.Rd:100: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:101: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:102: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:103: Lost braces in \itemize; meant \describe ?
checkRd: (-1) tpsSim.Rd:107: Lost braces; missing escapes or markup?
107 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \code{X} which is expanded via the \code{expandX} argument. Each exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention.
| ^
Check History
NOTE 0 OK · 14 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE Mar 10, 2026
NOTE
r-devel-linux-x86_64-debian-clang
CRAN incoming feasibility
Maintainer: ‘Sebastien Haneuse <shaneuse@hsph.harvard.edu>’
No Authors@R field in DESCRIPTION.
Please add one, modifying
Authors@R: c(person(given = "Sebastien",
family = "Haneuse",
role = c("aut", "cre"
...[truncated]...
e = "aut"))
as necessary.
Package CITATION file contains call(s) to old-style personList() or
as.personList(). Please use c() on person objects instead.
Package CITATION file contains call(s) to old-style citEntry(). Please
use bibentry() instead.
NOTE
r-devel-linux-x86_64-debian-gcc
CRAN incoming feasibility
Maintainer: ‘Sebastien Haneuse <shaneuse@hsph.harvard.edu>’
No Authors@R field in DESCRIPTION.
Please add one, modifying
Authors@R: c(person(given = "Sebastien",
family = "Haneuse",
role = c("aut", "cre"
...[truncated]...
e = "aut"))
as necessary.
Package CITATION file contains call(s) to old-style personList() or
as.personList(). Please use c() on person objects instead.
Package CITATION file contains call(s) to old-style citEntry(). Please
use bibentry() instead.
NOTE
r-devel-linux-x86_64-fedora-clang
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-devel-linux-x86_64-fedora-gcc
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-devel-macos-arm64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-devel-windows-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-patched-linux-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-release-linux-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-release-macos-arm64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-release-macos-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-release-windows-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-oldrel-macos-arm64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-oldrel-macos-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^
NOTE
r-oldrel-windows-x86_64
Rd files
checkRd: (-1) ccPower.Rd:57: Lost braces; missing escapes or markup?
57 | The correspondence between \code{betaTruth} and \code{X}, specifically the ordering of elements, is based on successive use of \code{\link{factor}} to each column of \cod
...[truncated]...
^