Check results for 'latentcor'

using R version 4.4.0 (2024-04-24)
using platform: x86_64-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.3.1
using session charset: UTF-8
checking for file ‘latentcor/DESCRIPTION’ ... OK
checking extension type ... Package
this is package ‘latentcor’ version ‘2.0.1’
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 ‘latentcor’ can be installed ... [21s/23s] OK See the install log for details.
used C compiler: ‘Apple clang version 14.0.3 (clang-1403.0.22.14.1)’
used SDK: ‘MacOSX11.3.sdk’
checking installed package size ... OK
checking package directory ... 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 ... OK
checking code files for non-ASCII characters ... OK
checking R files for syntax errors ... OK
checking whether the package can be loaded ... [3s/3s] 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 ... [2s/3s] OK
checking whether the namespace can be unloaded cleanly ... [3s/3s] OK
checking loading without being on the library search path ... [3s/3s] OK
checking whether startup messages can be suppressed ... [3s/3s] 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/10s] OK
checking Rd files ... [0s/0s] NOTE checkRd: (-1) evaluation.Rd:38: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:39: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:40: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:41: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:42: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:43: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:44: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:45: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:46: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:47: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:48: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:49: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:50: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:51: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:52: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:53: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:54: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:55: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:56: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:57: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:58: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) evaluation.Rd:59: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) gen_data.Rd:35: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) gen_data.Rd:36-37: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) get_types.Rd:17: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) interpolation.Rd:23: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) interpolation.Rd:24: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) latentcor.Rd:38: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) latentcor.Rd:39: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) latentcor.Rd:40: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) latentcor.Rd:41: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) latentcor.Rd:42: Lost braces in \itemize; \value handles \item{}{} directly
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 R/sysdata.rda ... OK
checking line endings in C/C++/Fortran sources/headers ... OK
checking line endings in Makefiles ... OK
checking compilation flags in Makevars ... OK
checking for GNU extensions in Makefiles ... OK
checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
checking use of PKG_*FLAGS in Makefiles ... OK
checking compiled code ... OK
checking installed files from ‘inst/doc’ ... OK
checking files in ‘vignettes’ ... OK
checking examples ... [4s/4s] OK
checking for unstated dependencies in ‘tests’ ... OK
checking tests ... [6s/6s] OK Running ‘testthat.R’ [6s/6s]
checking for unstated dependencies in vignettes ... OK
checking package vignettes ... OK
checking re-building of vignette outputs ... [22s/24s] OK
checking PDF version of manual ... [6s/7s] OK
DONE Status: 1 NOTE
using check arguments '--no-clean-on-error '