• using R Under development (unstable) (2024-12-10 r87437)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     clang version 19.1.5     flang-new version 19.1.5
• running under: Fedora Linux 36 (Workstation Edition)
• using session charset: UTF-8
• using option ‘--no-stop-on-test-error’
• checking for file ‘RNCEP/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘RNCEP’ version ‘1.0.10’
• 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 ‘RNCEP’ can be installed ... [28s/33s] OK See the install log for details.
• checking installed package size ... OK
• checking package 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 ... OK
• checking whether the package can be loaded with stated dependencies ... OK
• checking whether the package can be unloaded cleanly ... OK
• checking whether the namespace can be loaded with stated dependencies ... OK
• checking whether the namespace can be unloaded cleanly ... OK
• checking loading without being on the library search path ... 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 ... [57s/66s] OK
• checking Rd files ... NOTE checkRd: (-1) NCEP.track2kml.Rd:36: Lost braces     36 | There are several options for specifying \code{col.scheme}. A single color may be specified for all points (using e.g. \code{'red'}, \code{2}, or \code{"#FF0000"}), specific colors may be given for each point (e.g. \code{c('red','blue','green', etc.)} or code{c('#FF0000','#0000FF','#00FF00', etc.)}), or the function can automatically assign colors, according to the values in \code{clo.variable}, if \code{col.scheme} is any color palette in \code{\link[RColorBrewer]{display.brewer.all}} or one of the recognizezd R color palettes (i.e. \code{'rainbow'}, \code{'heat.colors'}, \code{'terrain.colors'}, \code{'topo.colors'}, \code{'cm.colors'}, or \code{'bpy.colors'}). An alpha value (0-255) may be supplied to \code{point.alpha} to adjust transparencies.        | ^
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... INFO Undeclared packages ‘fossil’, ‘raster’ in Rd xrefs
• 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 ... OK
• checking LazyData ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking examples ... OK
• checking PDF version of manual ... [9s/13s] OK
• checking HTML version of manual ... OK
• checking for non-standard things in the check directory ... OK
• checking for detritus in the temp directory ... OK
• DONE

Status: 1 NOTE