• using R version 4.4.2 (2024-10-31)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     gcc-14 (Debian 14.2.0-8) 14.2.0     GNU Fortran (Debian 14.2.0-8) 14.2.0
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘hierNet/DESCRIPTION’ ... OK
• this is package ‘hierNet’ version ‘1.9’
• 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 serialization versions ... OK
• checking whether package ‘hierNet’ can be installed ... OK See the install log for details.
• used C compiler: ‘gcc-14 (Debian 14.2.0-8) 14.2.0’
• checking package directory ... OK
• checking for future file timestamps ... 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 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 ... [7s/9s] OK
• checking Rd files ... [0s/0s] NOTE checkRd: (-1) hierNet.Rd:28: Lost braces; missing escapes or markup?     28 | terms, th_{jj}X_j^2, in the model. Default TRUE.}        | ^ checkRd: (-1) hierNet.logistic.Rd:30: Lost braces; missing escapes or markup?     30 | terms, th_{jj}X_j^2, in the model. Default TRUE.}        | ^ checkRd: (-1) hierNet.logistic.Rd:63: Lost braces     63 | \seealso{\link{predict.hierNet.logistic},link{hierNet.logistic.path}}        | ^ checkRd: (-1) hierNet.logistic.path.Rd:39: Lost braces; missing escapes or markup?     39 | terms, th_{jj}X_j^2, in the model. Default TRUE.}        | ^ checkRd: (-1) hierNet.path.Rd:38: Lost braces; missing escapes or markup?     38 | terms, th_{jj}X_j^2, in the model. Default TRUE.}        | ^
• checking Rd metadata ... OK
• checking Rd line widths ... 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 line endings in C/C++/Fortran sources/headers ... OK
• checking pragmas in C/C++ headers and code ... OK
• checking compilation flags used ... OK
• checking compiled code ... OK
• checking examples ... [8s/9s] OK
• checking PDF version of manual ... [4s/6s] OK
• checking HTML version of manual ... [1s/1s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 1 NOTE