• using R version 4.4.0 alpha (2024-03-31 r86238)
• using platform: aarch64-apple-darwin20
• R was compiled by     Apple clang version 14.0.0 (clang-1400.0.29.202)     GNU Fortran (GCC) 12.2.0
• running under: macOS Ventura 13.4
• using session charset: UTF-8
• checking for file ‘pems.utils/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘pems.utils’ version ‘0.2.29.1’
• 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 ‘pems.utils’ can be installed ... [19s/20s] OK See the install log for details.
• used C++ compiler: ‘Apple clang version 14.0.0 (clang-1400.0.29.202)’
• used SDK: ‘MacOSX11.3.sdk’
• 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 ... [4s/5s] OK
• checking whether the package can be loaded with stated dependencies ... [4s/5s] OK
• checking whether the package can be unloaded cleanly ... [4s/4s] OK
• checking whether the namespace can be loaded with stated dependencies ... [4s/4s] OK
• checking whether the namespace can be unloaded cleanly ... [4s/5s] OK
• checking loading without being on the library search path ... [4s/4s] 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 ... [14s/14s] OK
• checking Rd files ... [0s/0s] NOTE checkRd: (-1) 5.1.pems.plots.Rd:212: Lost braces; missing escapes or markup?    212 | (Logical or character) For {WatsonPlot}, how to        | ^ checkRd: (-1) 5.1.pems.plots.Rd:221: Lost braces; missing escapes or markup?    221 | (numeric) For {WatsonPlot}, pre-set plot types:        | ^ checkRd: (-1) 6.2.check.functions.Rd:189: Lost braces    189 | If a parent function is identified as \code{fun.name} and the check case (code{input},        | ^ checkRd: (-1) 7.1.vsp.code.Rd:89: Lost braces     89 | code{\link{common.calculations}} for further details.        | ^ checkRd: (-1) 7.2.emissions.code.Rd:90: Lost braces     90 | emissions calculation methods. It accepts an input code{conc} which it checks and passes        | ^ checkRd: (-1) 8.1.tidyverse.tools.Rd:139: Lost braces    139 | (\code{pems}, code{data.frame}, etc) to        | ^
• checking Rd metadata ... 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 compiled code ... OK
• checking examples ... [6s/7s] OK
• checking PDF version of manual ... [6s/7s] OK
• DONE Status: 1 NOTE
• using check arguments '--no-clean-on-error '