CRAN Package Check Results for Package pcoxtime

Last updated on 2024-02-26 23:03:47 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.0.4 50.93 152.23 203.16 NOTE
r-devel-linux-x86_64-debian-gcc 1.0.4 41.66 114.54 156.20 NOTE
r-devel-linux-x86_64-fedora-clang 1.0.4 259.55 NOTE
r-devel-linux-x86_64-fedora-gcc 1.0.4 267.94 NOTE
r-devel-windows-x86_64 1.0.4 43.00 149.00 192.00 NOTE
r-patched-linux-x86_64 1.0.4 47.45 147.43 194.88 NOTE
r-release-linux-x86_64 1.0.4 47.85 145.65 193.50 NOTE
r-release-macos-arm64 1.0.4 67.00 NOTE
r-release-macos-x86_64 1.0.4 122.00 NOTE
r-release-windows-x86_64 1.0.4 53.00 176.00 229.00 NOTE
r-oldrel-macos-arm64 1.0.4 65.00 OK
r-oldrel-windows-x86_64 1.0.4 55.00 171.00 226.00 OK

Check Details

Version: 1.0.4
Check: C++ specification
Result: NOTE Specified C++11: please drop specification unless essential 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

Version: 1.0.4
Check: Rd files
Result: NOTE checkRd: (-1) pcoxtimecv.Rd:51: Lost braces; missing escapes or markup? 51 | \item{foldids}{an optional sequence of values between \code{1} and {nfolds} specifying what fold each observation is in. This is important when comparing performance across models. If specified, \code{nfolds} can be missing.} | ^ checkRd: (-1) pcoxtimecv.Rd:89: Lost braces 89 | If more than one \code{alphas} is specified, say code{(0.2, 0.5, 1)}, the \code{pcoxtimecv} will search (experimental) for optimal values for alpha with respect to the corresponding lambda values. In this case, optimal alpha and lambda sequence will be returned, i.e., the \code{(alphas, lambdas)} pair that corresponds to the lowest predicted cross-validated error (likelihood deviance). | ^ checkRd: (-1) simtdc.Rd:67: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) simtdc.Rd:69: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) simtdc.Rd:70: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) simtdc.Rd:71: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) simtdc.Rd:72: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) simtdc.Rd:73: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) simtdc.Rd:74: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) simtdc.Rd:76: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) simtdc.Rd:77: Lost braces in \itemize; \value handles \item{}{} directly Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang

Version: 1.0.4
Check: Rd \usage sections
Result: NOTE Documented arguments not in \usage in Rd file 'getResponse.Rd': ‘model’ Functions with \usage entries need to have the appropriate \alias entries, and all their arguments documented. The \usage entries must correspond to syntactically valid R code. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. 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