• using R Under development (unstable) (2024-11-06 r87293)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     Debian clang version 19.1.2 (2)     Debian flang-new version 19.1.2 (2)
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘WaverideR/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘WaverideR’ version ‘0.3.2’
• 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 whether package ‘WaverideR’ 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 ... [5s/8s] OK
• checking whether the package can be loaded with stated dependencies ... [4s/6s] OK
• checking whether the package can be unloaded cleanly ... [4s/7s] OK
• checking whether the namespace can be loaded with stated dependencies ... [4s/5s] OK
• checking whether the namespace can be unloaded cleanly ... [5s/7s] OK
• checking loading without being on the library search path ... [5s/6s] 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 ... [51s/63s] OK
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) anchor_points_grey.Rd:9: Lost braces      9 | Zeeden et al., (2013) and anchored to the code{\link{astrosignal_example}} \cr        | ^ checkRd: (-1) retrack_wt_MC.Rd:206: Lost braces    206 | be off in certain intervals. the link[WaverideR]{retrack_wt_MC} mitigates        | ^ checkRd: (-1) retrack_wt_MC.Rd:40: Lost braces     40 | link[WaverideR]{analyze_wavelet} wavelet function        | ^ checkRd: (-1) retrack_wt_MC.Rd:41: Lost braces     41 | To create a list use the link[base]{list} function}        | ^ checkRd: (-1) retrack_wt_MC.Rd:44: Lost braces     44 | To create the matrix use the link[base]{cbind} function and only add the        | ^
• 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:   loess_auto.Rd: loess.as 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 LazyData ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking examples ... [14s/16s] OK Examples with CPU (user + system) or elapsed time > 5s                user system elapsed extract_power 3.901 0.383 5.01
• checking PDF version of manual ... [8s/11s] OK
• checking HTML version of manual ... [4s/7s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 2 NOTEs