• using R version 4.4.0 (2024-04-24)
  • using platform: x86_64-apple-darwin20
  • R was compiled by     Apple clang version 14.0.0 (clang-1400.0.29.202)     GNU Fortran (GCC) 12.2.0
  • running under: macOS Ventura 13.3.1
  • using session charset: UTF-8
  • checking for file ‘osDesign/DESCRIPTION’ ... OK
  • checking extension type ... Package
  • this is package ‘osDesign’ version ‘1.8’
  • checking package namespace information ... OK
  • checking package dependencies ... OK
  • checking if this is a source package ... OK
  • checking if there is a namespace ... OK
  • checking for executable files ... OK
  • checking for hidden files and directories ... OK
  • checking for portable file names ... OK
  • checking for sufficient/correct file permissions ... OK
  • checking whether package ‘osDesign’ can be installed ... [3s/4s] OK See the install log for details.
  • checking installed package size ... OK
  • checking package directory ... OK
  • checking DESCRIPTION meta-information ... OK
  • checking top-level files ... OK
  • checking for left-over files ... OK
  • checking index information ... OK
  • checking package subdirectories ... OK
  • checking code files for non-ASCII characters ... OK
  • checking R files for syntax errors ... OK
  • checking whether the package can be loaded ... [0s/0s] OK
  • checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
  • checking whether the package can be unloaded cleanly ... [0s/0s] OK
  • checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
  • checking whether the namespace can be unloaded cleanly ... [0s/0s] OK
  • checking loading without being on the library search path ... [0s/0s] OK
  • checking dependencies in R code ... OK
  • checking S3 generic/method consistency ... OK
  • checking replacement functions ... OK
  • checking foreign function calls ... OK
  • checking R code for possible problems ... [4s/5s] OK
  • checking Rd files ... [0s/0s] 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.        | ^
  • checking Rd metadata ... OK
  • checking Rd cross-references ... OK
  • checking for missing documentation entries ... OK
  • checking for code/documentation mismatches ... OK
  • checking Rd \usage sections ... OK
  • checking Rd contents ... OK
  • checking for unstated dependencies in examples ... OK
  • checking contents of ‘data’ directory ... OK
  • checking data for non-ASCII characters ... [0s/0s] OK
  • checking data for ASCII and uncompressed saves ... OK
  • checking examples ... [8s/8s] OK
  • checking PDF version of manual ... [6s/9s] OK
  • DONE Status: 1 NOTE
  • using check arguments '--no-clean-on-error '