• 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-6) 14.2.0     GNU Fortran (Debian 14.2.0-6) 14.2.0
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘doremi/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘doremi’ version ‘1.0.0’
• 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 ‘doremi’ can be installed ... OK See the install log for details.
• 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 ... NOTE Problems with news in ‘NEWS.md’:   Cannot extract version info from the following section titles:     New features
• 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 ... [3s/3s] OK
• checking whether the package can be unloaded cleanly ... [3s/3s] OK
• checking whether the namespace can be loaded with stated dependencies ... [3s/4s] OK
• checking whether the namespace can be unloaded cleanly ... [3s/4s] OK
• checking loading without being on the library search path ... [3s/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 ... [18s/24s] OK
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) analyze.1order.Rd:49: Lost braces     49 | Although only the first derivative is used here, using a higher order can enhance derivative estimation (see \doi{10.1080/00273171.2015.1123138}{Chow et al.(2016)})}        | ^ checkRd: (-1) analyze.2order.Rd:44: Lost braces     44 | 2 in second order differential equations), for instance, order=4 might enhance derivative estimation (see \doi{10.1080/00273171.2015.1123138}{Chow et al.(2016)})}        | ^ checkRd: (-1) calculate.fda.Rd:29: Lost braces     29 | method described in several sources, such as in \doi{10.1007/b98888}{Ramsay et al. (2009)}        | ^ checkRd: (-1) calculate.fda.Rd:30: Lost braces     30 | and \doi{10.1080/00273171.2015.1123138}{Chow et al. (2016)}.        | ^ checkRd: (-1) calculate.glla.Rd:34: Lost braces     34 | described in \doi{10.4324/9780203864746}{Boker et al.(2010)}.        | ^ checkRd: (-1) calculate.gold.Rd:33: Lost braces     33 | method described in \doi{10.1080/00273171.2010.498294}{Deboeck (2010)}. The code available on this paper was extracted and adapted for non constant time steps.        | ^ checkRd: (-1) optimum_param.Rd:47: Lost braces     47 | Using a higher order can enhance derivative estimation (see \doi{10.1080/00273171.2015.1123138}{Chow et al.(2016)})}        | ^ checkRd: (-1) rotation.Rd:37: Lost braces     37 | \doi{10.1016/j.yhbeh.2012.12.007}{(Courvoisier et al., 2013)}.        | ^
• 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 installed files from ‘inst/doc’ ... OK
• checking files in ‘vignettes’ ... OK
• checking examples ... [30s/39s] OK Examples with CPU (user + system) or elapsed time > 5s                   user system elapsed optimum_param 5.105 0.106 6.256 analyze.2order 4.837 0.101 6.314 plot.doremiparam 4.745 0.010 7.156
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... OK
• checking re-building of vignette outputs ... [131s/180s] OK
• checking PDF version of manual ... [5s/7s] OK
• checking HTML version of manual ... [1s/2s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 2 NOTEs