* using log directory ‘/srv/hornik/tmp/CRAN/POPInf.Rcheck’ * using R Under development (unstable) (2024-02-16 r85931) * using platform: x86_64-pc-linux-gnu * R was compiled by Debian clang version 17.0.6 (5) Debian flang-new version 17.0.6 (5) * running under: Debian GNU/Linux trixie/sid * using session charset: UTF-8 * checking for file ‘POPInf/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘POPInf’ version ‘1.0.0’ * package encoding: UTF-8 * checking CRAN incoming feasibility ... [3s/4s] NOTE Maintainer: ‘Jiacheng Miao ’ New submission Possibly misspelled words in DESCRIPTION: Miao (8:188) al (8:196) et (8:193) * 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 ‘POPInf’ can be installed ... [1s/1s] OK * checking package directory ... OK * checking for future file timestamps ... OK * checking DESCRIPTION meta-information ... NOTE Malformed Description field: should contain one or more complete sentences. * checking top-level files ... NOTE File LICENSE is not mentioned in the DESCRIPTION file. * checking for left-over files ... OK * checking index information ... OK * checking package subdirectories ... OK * checking R 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 A : : no visible global function definition for ‘density’ A_single : : no visible global function definition for ‘density’ A_single: no visible binding for global variable ‘Y_lab’ A_single: no visible binding for global variable ‘X_lab’ A_single: no visible binding for global variable ‘X_unlab’ Sigma_cal: no visible global function definition for ‘cov’ est_ini: no visible global function definition for ‘lm’ est_ini: no visible global function definition for ‘quantile’ est_ini: no visible global function definition for ‘glm’ est_ini: no visible binding for global variable ‘binomial’ est_ini: no visible binding for global variable ‘poisson’ optim_weights: no visible global function definition for ‘optim’ pop_M: no visible global function definition for ‘pnorm’ pop_M: no visible global function definition for ‘qnorm’ sim_data: no visible global function definition for ‘rnorm’ sim_data: no visible global function definition for ‘median’ sim_data: no visible global function definition for ‘predict’ Undefined global functions or variables: X_lab X_unlab Y_lab binomial cov density glm lm median optim pnorm poisson predict qnorm quantile rnorm Consider adding importFrom("stats", "binomial", "cov", "density", "glm", "lm", "median", "optim", "pnorm", "poisson", "predict", "qnorm", "quantile", "rnorm") to your NAMESPACE file. * checking Rd files ... [0s/0s] OK * checking Rd metadata ... OK * checking Rd line widths ... NOTE Rd file 'pop_M.Rd': \examples lines wider than 100 characters: pop_M(Y_lab = Y_lab, Yhat_lab = Yhat_lab, Yhat_unlab = Yhat_unlab, alpha = 0.05, quant = 0.75, method = "quantile") These lines will be truncated in the PDF manual. * checking Rd cross-references ... OK * checking for missing documentation entries ... WARNING Undocumented code objects: ‘A’ ‘A_single’ ‘Sigma_cal’ ‘est_ini’ ‘link_Hessian’ ‘link_grad’ ‘mean_psi’ ‘mean_psi_pop’ ‘optim_est’ ‘optim_weights’ ‘psi’ ‘sim_data’ 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 ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking examples ... [1s/1s] OK * 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: 1 WARNING, 5 NOTEs