* using log directory 'd:/RCompile/CRANincoming/R-devel/NetworkReg.Rcheck'
* using R Under development (unstable) (2024-10-16 r87241 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 'NetworkReg/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'NetworkReg' version '2.0'
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [11s] NOTE
Maintainer: 'Jianxiang Wang <jw1881@scarletmail.rutgers.edu>'

New maintainer:
  Jianxiang Wang <jw1881@scarletmail.rutgers.edu>
Old maintainer(s):
  Tianxi Li <tianxili@umn.edu>

The Description field contains
  is originally proposed by Le and Li (2022) <arXiv:2007.00803> and is
  <arXiv:2410.01163> further extends the framework to generalized linear
Please refer to arXiv e-prints via their arXiv DOI <doi:10.48550/arXiv.YYMM.NNNNN>.
* 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 serialization versions ... OK
* checking whether package 'NetworkReg' can be installed ... OK
* checking installed package size ... 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 <jw1881@scarletmail.rutgers.edu> [aut, cre]
  Tianxi Li <tianxili@umn.edu> [aut, cre]
Maintainer field differs from that derived from Authors@R
  Maintainer: 'Jianxiang Wang <jw1881@scarletmail.rutgers.edu>'
  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 ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... 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 ... [22s] 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 ... 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 ... OK
* checking PDF version of manual ... [22s] OK
* checking HTML version of manual ... OK
* DONE
Status: 5 NOTEs