• using R Under development (unstable) (2024-10-01 r87205)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     Debian clang version 19.1.0 (4)     Debian flang-new version 19.1.0 (4)
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘TSclust/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘TSclust’ version ‘1.3.1’
• 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 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 ‘TSclust’ can be installed ... OK See the install log for details.
• 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 ... [3s/4s] OK
• checking whether the package can be loaded with stated dependencies ... [2s/3s] OK
• checking whether the package can be unloaded cleanly ... [2s/3s] OK
• checking whether the namespace can be loaded with stated dependencies ... [2s/3s] OK
• checking whether the namespace can be unloaded cleanly ... [3s/3s] OK
• checking loading without being on the library search path ... [3s/3s] 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 ... [23s/30s] OK
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) diss.AR.LPC.CEPS.Rd:39: Lost braces; missing escapes or markup?     39 | If \code{order.x} or {order.y} are \code{NULL}, their respective series will be fitted automatically using a AR model.        | ^ checkRd: (-1) diss.AR.PIC.Rd:31: Lost braces; missing escapes or markup?     31 | If \code{order.x} or {order.y} are \code{NULL}, their respective series will be fitted automatically using a AR model. If \code{permissive} is \code{TRUE} and no AR order is found automatically, an AR order of 1 will be imposed, if this case fails, then no order can be found and the function produces an error.        | ^
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors:   diss.DTWARP.Rd: pdc   diss.FRECHET.Rd: longitudinalData   diss.PDC.Rd: pdc   diss.Rd: pdc Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages.
• 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 ... [16s/23s] OK Examples with CPU (user + system) or elapsed time > 5s                user system elapsed diss.PRED 3.608 0.655 5.330 diss.SPEC.LLR 3.170 0.089 5.058
• checking PDF version of manual ... [6s/8s] OK
• checking HTML version of manual ... [2s/4s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 2 NOTEs