CRAN Package Check Results for Package osDesign

Last updated on 2024-12-25 17:49:19 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.8 4.61 45.40 50.01 NOTE
r-devel-linux-x86_64-debian-gcc 1.8 3.07 31.73 34.80 NOTE
r-devel-linux-x86_64-fedora-clang 1.8 78.32 NOTE
r-devel-linux-x86_64-fedora-gcc 1.8 78.26 NOTE
r-devel-windows-x86_64 1.8 5.00 64.00 69.00 NOTE
r-patched-linux-x86_64 1.8 4.88 42.69 47.57 NOTE
r-release-linux-x86_64 1.8 4.49 42.83 47.32 NOTE
r-release-macos-arm64 1.8 26.00 NOTE
r-release-macos-x86_64 1.8 42.00 NOTE
r-release-windows-x86_64 1.8 5.00 62.00 67.00 NOTE
r-oldrel-macos-arm64 1.8 31.00 OK
r-oldrel-macos-x86_64 1.8 42.00 OK
r-oldrel-windows-x86_64 1.8 6.00 66.00 72.00 OK

Check Details

Version: 1.8
Check: Rd files
Result: NOTE 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: Lost braces in \itemize; meant \describe ? 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 exposure that is expanded must conform to a {0, 1, 2, ...} integer-based coding convention. | ^ checkRd: (-1) phaseI.Rd:55: Lost braces; missing escapes or markup? 55 | 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) tpsPower.Rd:67: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsPower.Rd:68: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsPower.Rd:69: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsPower.Rd:70: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsPower.Rd:71: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsPower.Rd:77: Lost braces; missing escapes or markup? 77 | 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) tpsSim.Rd:86: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsSim.Rd:87: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsSim.Rd:88: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsSim.Rd:89: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsSim.Rd:90: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsSim.Rd:96: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsSim.Rd:97: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsSim.Rd:98: Lost braces in \itemize; meant \describe ? checkRd: (-1) tpsSim.Rd:99: Lost braces in \itemize; 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. | ^ Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64