* using log directory ‘/srv/hornik/tmp/CRAN_pretest/GLHD.Rcheck’ * using R Under development (unstable) (2024-10-22 r87265) * using platform: x86_64-pc-linux-gnu * R was compiled by Debian clang version 19.1.1 (1) Debian flang-new version 19.1.1 (1) * running under: Debian GNU/Linux trixie/sid * using session charset: UTF-8 * checking for file ‘GLHD/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘GLHD’ version ‘0.0.1’ * package encoding: UTF-8 * checking CRAN incoming feasibility ... [3s/3s] NOTE Maintainer: ‘Wenlong Li ’ New submission No Authors@R field in DESCRIPTION. Please add one, modifying Authors@R: c(person(given = "Wenlong", family = "Li", role = c("aut", "cre"), email = "wlli1@bjtu.edu.cn"), person(given = "Jian-Feng", family = "Yang", role = "aut"), person(given = "Peter", family = "Chien", role = "aut")) as necessary. The Title field should be in title case. Current version is: ‘Controlling correlations in grouped Latin hypercube designs’ In title case that is: ‘Controlling Correlations in Grouped Latin Hypercube Designs’ * 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 serialization versions ... OK * checking whether package ‘GLHD’ can be installed ... [1s/1s] OK * checking package directory ... OK * checking for future file timestamps ... 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 ... [0s/0s] OK * checking whether the package can be loaded with stated dependencies ... [0s/0s] OK * checking whether the package can be unloaded cleanly ... [0s/0s] OK * checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK * checking whether the namespace can be unloaded cleanly ... [0s/0s] OK * checking loading without being on the library search path ... [0s/0s] 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 ... [2s/2s] NOTE Owen1994: no visible global function definition for ‘residuals’ Owen1994: no visible global function definition for ‘lm’ Owen_between: no visible global function definition for ‘residuals’ Owen_between: no visible global function definition for ‘lm’ cor_within: no visible global function definition for ‘cor’ cor_within_between: no visible global function definition for ‘cor’ rms: no visible global function definition for ‘cor’ Undefined global functions or variables: cor lm residuals Consider adding importFrom("stats", "cor", "lm", "residuals") to your NAMESPACE file. * checking Rd files ... [0s/0s] OK * checking Rd metadata ... OK * checking Rd line widths ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... WARNING Undocumented code objects: ‘Owen1994’ ‘Owen_between’ ‘Owen_within’ ‘Owen_within_kth_group’ ‘affiliation’ ‘cor_within’ ‘cor_within_between’ ‘tri’ All user-level objects in a package should have documentation entries. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... WARNING Undocumented arguments in Rd file 'GroupLHD.Rd' ‘u’ Documented arguments not in \usage in Rd file 'GroupLHD.Rd': ‘u=(u1’ ‘ug))’ ‘p=u1+...+ug’ ‘...’ Undocumented arguments in Rd file 'rms.Rd' ‘x’ Documented arguments not in \usage in Rd file 'rms.Rd': ‘D’ 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 examples ... [7s/7s] NOTE Examples with CPU (user + system) or elapsed time > 5s user system elapsed GroupLHD 6.834 0 6.835 * checking PDF version of manual ... [2s/2s] OK * checking HTML version of manual ... [0s/0s] OK * checking for non-standard things in the check directory ... OK * checking for detritus in the temp directory ... OK * DONE Status: 2 WARNINGs, 3 NOTEs