* using log directory ‘/srv/hornik/tmp/CRAN_pretest/NetworkReg.Rcheck’ * using R Under development (unstable) (2024-10-16 r87241) * using platform: x86_64-pc-linux-gnu * R was compiled by Debian clang version 18.1.8 (9) Debian flang-new version 18.1.8 (9) * running under: Debian GNU/Linux trixie/sid * using session charset: UTF-8 * checking for file ‘NetworkReg/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘NetworkReg’ version ‘2.0’ * package encoding: UTF-8 * checking CRAN incoming feasibility ... [3s/4s] NOTE Maintainer: ‘Jianxiang Wang ’ New maintainer: Jianxiang Wang Old maintainer(s): Tianxi Li The Description field contains is originally proposed by Le and Li (2022) and is further extends the framework to generalized linear Please refer to arXiv e-prints via their arXiv DOI . * 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 ‘NetworkReg’ can be installed ... [6s/6s] OK * checking package directory ... OK * checking for future file timestamps ... OK * checking DESCRIPTION meta-information ... NOTE Authors@R field gives more than one person with maintainer role: Jianxiang Wang [aut, cre] Tianxi Li [aut, cre] Maintainer field differs from that derived from Authors@R Maintainer: ‘Jianxiang Wang ’ Authors@R: ‘’ * 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/2s] OK * checking whether the package can be loaded with stated dependencies ... [1s/1s] OK * checking whether the package can be unloaded cleanly ... [1s/1s] OK * checking whether the namespace can be loaded with stated dependencies ... [1s/1s] OK * checking whether the namespace can be unloaded cleanly ... [2s/2s] OK * checking loading without being on the library search path ... [2s/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 ... [8s/8s] NOTE SP.Inf.Linear: no visible global function definition for ‘pnorm’ SP.Inf.Linear: no visible global function definition for ‘qnorm’ SP.Inf.Linear: no visible global function definition for ‘pchisq’ SP.Inf.Logistic: no visible global function definition for ‘glm’ SP.Inf.Logistic: no visible global function definition for ‘vcov’ SP.Inf.Logistic: no visible global function definition for ‘qnorm’ SP.Inf.Logistic: no visible global function definition for ‘qchisq’ SP.Inf.Logistic: no visible global function definition for ‘pchisq’ SP.Inf.Logistic: no visible global function definition for ‘pnorm’ SP.Inf.Poisson: no visible global function definition for ‘glm’ SP.Inf.Poisson: no visible global function definition for ‘poisson’ SP.Inf.Poisson: no visible global function definition for ‘vcov’ SP.Inf.Poisson: no visible global function definition for ‘qnorm’ SP.Inf.Poisson: no visible global function definition for ‘qchisq’ SP.Inf.Poisson: no visible global function definition for ‘pchisq’ SP.Inf.Poisson: no visible global function definition for ‘pnorm’ net.gen.from.P: no visible global function definition for ‘runif’ Undefined global functions or variables: glm pchisq pnorm poisson qchisq qnorm runif vcov Consider adding importFrom("stats", "glm", "pchisq", "pnorm", "poisson", "qchisq", "qnorm", "runif", "vcov") to your NAMESPACE file. * checking Rd files ... [0s/0s] NOTE checkRd: (-1) SP.Inf.Rd:35: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) SP.Inf.Rd:36: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) SP.Inf.Rd:37: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) SP.Inf.Rd:38: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) SP.Inf.Rd:39: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) SP.Inf.Rd:40: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) SP.Inf.Rd:41: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) SP.Inf.Rd:42: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) SP.Inf.Rd:43: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) SP.Inf.Rd:44: Lost braces in \itemize; \value handles \item{}{} directly * checking Rd metadata ... OK * checking Rd line widths ... NOTE Rd file 'SP.Inf.Rd': \usage lines wider than 90 characters: SP.Inf(X, Y, A, K, model="linear", r = NULL, sigma2 = NULL, thr = NULL, alpha.CI = 0.05,boot.thr = TRUE, boot.n = 50) These lines will be truncated in the PDF manual. * 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 examples ... [2s/2s] 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: 5 NOTEs