• using R Under development (unstable) (2024-11-13 r87330)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     Debian clang version 19.1.3 (1)     Debian flang-new version 19.1.3 (1)
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘lcmm/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘lcmm’ version ‘2.1.0’
• 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 ‘lcmm’ can be installed ... OK See the install log for details.
• used C compiler: ‘Debian clang version 19.1.3 (1)’
• used Fortran compiler: ‘Debian flang-new version 19.1.3 (1)’
• checking package directory ... OK
• checking for future file timestamps ... 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 ... [2s/2s] OK
• checking whether the package can be loaded with stated dependencies ... [2s/2s] OK
• checking whether the package can be unloaded cleanly ... [2s/2s] OK
• checking whether the namespace can be loaded with stated dependencies ... [2s/2s] OK
• checking whether the namespace can be unloaded cleanly ... [2s/2s] OK
• checking loading without being on the library search path ... [2s/2s] 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 ... [146s/177s] OK
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) Jointlcmm.Rd:377: Lost braces; missing escapes or markup?    377 | logscale=TRUE where {M_j} is the basis of cubic M-splines.        | ^ checkRd: (-1) externVar.Rd:123: Lost braces    123 | code{cor=BM(time)}. By default, no autocorrelated Gaussian process is added.}        | ^ checkRd: (-1) hlme.Rd:154: Lost braces    154 | item{best}{vector of parameter estimates in the same order as        | ^ checkRd: (-1) hlme.Rd:154-155: Lost braces    154 | item{best}{vector of parameter estimates in the same order as        | ^ checkRd: (-1) lcmm.Rd:269: Lost braces; missing escapes or markup?    269 | following transformation b_1 + b_2*I_1(Y(t)) + ... + b_{n+2} I_{n+1}(Y(t)),        | ^ checkRd: (-1) lcmm.Rd:269: Lost braces; missing escapes or markup?    269 | following transformation b_1 + b_2*I_1(Y(t)) + ... + b_{n+2} I_{n+1}(Y(t)),        | ^ checkRd: (-1) lcmm.Rd:270: Lost braces; missing escapes or markup?    270 | where I_1,...,I_{n+1} is the basis of quadratic I-splines. To constraint the        | ^ checkRd: (-1) lcmm.Rd:276: Lost braces; missing escapes or markup?    276 | transformation: Y(t)=c <=> b_c < L(t) <= b_{c+1} with b_0 = - infinity and        | ^ checkRd: (-1) lcmm.Rd:277: Lost braces; missing escapes or markup?    277 | b_{C+1}=+infinity. The number of parameters is reduced if some levels do not        | ^ checkRd: (-1) lcmm.Rd:279: Lost braces; missing escapes or markup?    279 | dataset, the corresponding threshold b_{c+1} is constrained to be the same        | ^ checkRd: (-1) lcmm.Rd:280: Lost braces; missing escapes or markup?    280 | as the previous one b_{c}. The number of parameters in the link function is        | ^ checkRd: (-1) lcmm.Rd:285: Lost braces; missing escapes or markup?    285 | b_{k}=b_{k-1}+(b_k^*)^2.        | ^ checkRd: (-1) lcmm.Rd:285: Lost braces; missing escapes or markup?    285 | b_{k}=b_{k-1}+(b_k^*)^2.        | ^ checkRd: (-1) multlcmm.Rd:322: Lost braces; missing escapes or markup?    322 | following transformation b_1 + b_2*I_1(Y(t)) + ... + b_{n+2} I_{n+1}(Y(t)),        | ^ checkRd: (-1) multlcmm.Rd:322: Lost braces; missing escapes or markup?    322 | following transformation b_1 + b_2*I_1(Y(t)) + ... + b_{n+2} I_{n+1}(Y(t)),        | ^ checkRd: (-1) multlcmm.Rd:323: Lost braces; missing escapes or markup?    323 | where I_1,...,I_{n+1} is the basis of quadratic I-splines. To constraint the        | ^ checkRd: (-1) multlcmm.Rd:330: Lost braces; missing escapes or markup?    330 | Y(t)=c <=> b_c < L(t) <= b_{c+1} with b_0 = - infinity and b_{C+1}=+infinity.        | ^ checkRd: (-1) multlcmm.Rd:330: Lost braces; missing escapes or markup?    330 | Y(t)=c <=> b_c < L(t) <= b_{c+1} with b_0 = - infinity and b_{C+1}=+infinity.        | ^ checkRd: (-1) multlcmm.Rd:333: Lost braces; missing escapes or markup?    333 | b_{k}=b_{k-1}+(b_k^*)^2.        | ^ checkRd: (-1) multlcmm.Rd:333: Lost braces; missing escapes or markup?    333 | b_{k}=b_{k-1}+(b_k^*)^2.        | ^ checkRd: (-1) print.lcmm.Rd:20: Lost braces     20 | for fitted latent class mixed-effects, or class \code{Jointlcmm}, code{mpjclmm} for        | ^
• 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 contents of ‘data’ directory ... OK
• checking data for non-ASCII characters ... [0s/0s] OK
• checking LazyData ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking line endings in C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking compilation flags in Makevars ... OK
• checking for GNU extensions in Makefiles ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking use of PKG_*FLAGS in Makefiles ... OK
• checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK
• checking pragmas in C/C++ headers and code ... OK
• checking compilation flags used ... OK
• checking compiled code ... OK
• checking usage of KIND in Fortran files ... OK
• checking installed files from ‘inst/doc’ ... OK
• checking files in ‘vignettes’ ... OK
• checking examples ... [14s/17s] OK
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... OK
• checking re-building of vignette outputs ... [5s/6s] OK
• checking PDF version of manual ... [8s/11s] OK
• checking HTML version of manual ... [4s/6s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 1 NOTE