* using log directory ‘/data/gannet/ripley/R/packages/tests-clang/rMR.Rcheck’
* using R Under development (unstable) (2024-04-24 r86484)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    clang version 18.1.4
    flang-new version 18.1.4
* running under: Fedora Linux 36 (Workstation Edition)
* using session charset: UTF-8
* using option ‘--no-stop-on-test-error’
* checking for file ‘rMR/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘rMR’ version ‘1.1.0’
* 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 ‘rMR’ can be installed ... OK
See 'https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-clang/rMR-00install.html' 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 ... [8s/12s] OK
* checking Rd files ... NOTE
checkRd: (-1) DO.unit.convert.Rd:24: Lost braces; missing escapes or markup?
    24 |     Units of dissolved oxygen concentration desired, i.e. to be converted to. Must be \code{"mg/L"}, \code{"PP"}, or {"pct"}.
       |                                                                                                                      ^
checkRd: (-1) MR.loops.Rd:80: Lost braces; missing escapes or markup?
    80 | Returns a list of 2. \code{$MR.summary} is of class {data.frame} with 3 columns: \code{$MR} (metabolic rate in user specified units, this is the same as the slope in each linear model), \code{$sd.slope} (standard deviation of slopes calculation), \code{$r.square} (adjusted r square value from each model). This second object is a list of \code{biglm} objects, each one representing a metabolic loop (see McDonnell and Chapman 2016). 
       |                                                     ^
checkRd: (-1) get.pcrit.Rd:27: Lost braces; missing escapes or markup?
    27 | Metabolic rate variable name, formatted as character. Default = \code{NULL}. If this argument takes a value, Pcrit will be calculated by regressing \code{MR.var.name} on \code{DO.var.name}. \code{time.var} and {time.interval} should, in this case, take no value. If \code{MR.var.name} is left as\code{NULL}, then instantaneous metabolic rates (MR) at specified time intervals (see \code{time.interval}) from \code{DO.var.name} and \code{time.var}.
       |                                                                                                                                                                                                                   ^
checkRd: (-1) tot.rss.Rd:35: Lost braces
    35 | code{\link{sumsq}}
       |     ^
checkRd: (-1) tot.rss.Rd:36: Lost braces
    36 | code{\link{get.pcrit}}
       |     ^
* 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 ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking examples ... [14s/18s] OK
* checking PDF version of manual ... [8s/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