* using log directory 'd:/Rcompile/CRANpkg/local/4.4/OpenRepGrid.Rcheck'
* using R version 4.4.0 RC (2024-04-16 r86468 ucrt)
* using platform: x86_64-w64-mingw32
* R was compiled by
    gcc.exe (GCC) 13.2.0
    GNU Fortran (GCC) 13.2.0
* running under: Windows Server 2022 x64 (build 20348)
* using session charset: UTF-8
* checking for file 'OpenRepGrid/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'OpenRepGrid' version '0.1.14'
* 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 hidden files and directories ... OK
* checking for portable file names ... OK
* checking whether package 'OpenRepGrid' can be installed ... OK
* 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 ... [2s] OK
* checking whether the package can be loaded with stated dependencies ... [2s] OK
* checking whether the package can be unloaded cleanly ... [1s] OK
* checking whether the namespace can be loaded with stated dependencies ... [2s] OK
* checking whether the namespace can be unloaded cleanly ... [2s] OK
* checking loading without being on the library search path ... [2s] OK
* checking whether startup messages can be suppressed ... [2s] 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 ... [18s] OK
* checking Rd files ... [3s] NOTE
checkRd: (-1) constructD.Rd:18: Lost braces
    18 | values for code{"columns"} and \code{"rows"}).}
       |                ^
checkRd: (-1) indexConflict2.Rd:43: Lost braces; missing escapes or markup?
    43 |                { Z_max x Z_mdn - Z_min <= crit }.
       |                ^
checkRd: (-1) indexConflict2.Rd:46: Lost braces; missing escapes or markup?
    46 |                { Z_min - Z_max x Z_mdn <= crit }.
       |                ^
checkRd: (-1) indexConflict2.Rd:56: Lost braces; missing escapes or markup?
    56 |        { a x Z_max x Z_mdn =< crit/a + Z_min}. This shows that a bigger value of \code{a}
       |        ^
checkRd: (-1) perturbate.Rd:18: Lost braces; missing escapes or markup?
    18 | range. Usually {-1, 1} are reasonable settings}
       |                ^
checkRd: (-1) settings.Rd:23: Lost braces in \itemize; meant \describe ?
checkRd: (-1) settings.Rd:24: Lost braces in \itemize; meant \describe ?
checkRd: (-1) settings.Rd:25: Lost braces in \itemize; meant \describe ?
checkRd: (-1) settings.Rd:26: Lost braces in \itemize; meant \describe ?
checkRd: (-1) settings.Rd:27: Lost braces in \itemize; meant \describe ?
checkRd: (-1) settings.Rd:28: Lost braces in \itemize; meant \describe ?
* 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 ... NOTE
Documented arguments not in \usage in Rd file 'bertinBase.Rd':
  'x' 'ratings' 'trim'

Documented arguments not in \usage in Rd file 'biplot3dBase2.Rd':
  'ext.sphere'

Documented arguments not in \usage in Rd file 'convertImportObjectToRepGridObject.Rd':
  'x'

Documented arguments not in \usage in Rd file 'convertScivescoImportObjectToRepGridObject.Rd':
  'x'

Documented arguments not in \usage in Rd file 'mapCoordinatesToColor.Rd':
  'color'

Documented arguments not in \usage in Rd file 'quasiDistributionDistanceSlater.Rd':
  'rep'

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter 'Writing R documentation files' in the 'Writing R
Extensions' manual.
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking contents of 'data' directory ... OK
* checking data for non-ASCII characters ... [2s] OK
* checking LazyData ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking examples ... [21s] OK
* checking for unstated dependencies in 'tests' ... OK
* checking tests ... [3s] OK
  Running 'testthat.R' [2s]
* checking PDF version of manual ... [27s] OK
* checking HTML version of manual ... [33s] OK
* DONE
Status: 2 NOTEs