• using R Under development (unstable) (2024-12-17 r87446 ucrt)
• using platform: x86_64-w64-mingw32
• R was compiled by     gcc.exe (GCC) 13.3.0     GNU Fortran (GCC) 13.3.0
• running under: Windows Server 2022 x64 (build 20348)
• using session charset: UTF-8
• checking for file 'BETS/DESCRIPTION' ... OK
• checking extension type ... Package
• this is package 'BETS' version '0.4.9'
• package encoding: UTF-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 hidden files and directories ... OK
• checking for portable file names ... OK
• checking whether package 'BETS' can be installed ... OK See the install log for details.
• checking installed package size ... OK
• checking package directory ... OK
• checking 'build' 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 ... [4s] OK
• checking whether the package can be loaded with stated dependencies ... [3s] OK
• checking whether the package can be unloaded cleanly ... [4s] OK
• checking whether the namespace can be loaded with stated dependencies ... [3s] OK
• checking whether the namespace can be unloaded cleanly ... [3s] OK
• checking loading without being on the library search path ... [4s] OK
• checking whether startup messages can be suppressed ... [4s] OK
• checking use of S3 registration ... 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 ... [15s] OK
• checking Rd files ... [1s] NOTE checkRd: (-1) BETSsearch.Rd:56: Lost braces     56 | \item{To exclude whole expressions from the search, surround them with code{' '} and insert a \code{~} before each of them.        | ^ checkRd: (-1) dummy.Rd:23: Lost braces; missing escapes or markup?     23 | \item{date}{a \code{list}. The periods for which the dummy must be set to one. Periods must be represented as {integer vectors}, as described for \code{start} and \code{end}.}        | ^ checkRd: (-1) dummy.Rd:25: Lost braces; missing escapes or markup?     25 | \item{from}{An \code{integer vector} The starting period of a sequence of perids for which the dummy must be set to one. Periods must be represented as {integer vectors}, as described for \code{start} and \code{end}.}        | ^ checkRd: (-1) dummy.Rd:27: Lost braces; missing escapes or markup?     27 | \item{to}{The ending period of a sequence of perids for which the dummy must be set to one. Periods must be represented as {integer vectors}, as described for \code{start} and \code{end}.}        | ^
• 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 LazyData ... INFO   'LazyData' is specified without a 'data' directory
• checking installed files from 'inst/doc' ... OK
• checking files in 'vignettes' ... OK
• checking examples ... [8s] OK
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... OK
• checking re-building of vignette outputs ... [7s] OK
• checking PDF version of manual ... [22s] OK
• checking HTML version of manual ... [10s] OK
• DONE

Status: 1 NOTE