* using log directory 'd:/RCompile/CRANincoming/R-devel/bdprecision.Rcheck'
* using R Under development (unstable) (2024-05-03 r86519 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 'bdprecision/DESCRIPTION' ... OK
* this is package 'bdprecision' version '0.0.1'
* package encoding: UTF-8
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Likang Li <lilikang@uic.edu.cn>'

New submission

Possibly misspelled words in DESCRIPTION:
  BD (6:14, 6:286, 6:472)
  OpenMP (6:557)
  thresholding (6:363)

Size of tarball: 24451471 bytes
* checking package namespace information ... OK
* checking package dependencies ... NOTE
Package in Depends/Imports which should probably only be in LinkingTo: 'RcppArmadillo'
* 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 'bdprecision' can be installed ... OK
* used C++ compiler: 'g++.exe (GCC) 13.2.0'
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking DESCRIPTION meta-information ... NOTE
Packages listed in more than one of Depends, Imports, Suggests, Enhances:
  'Rcpp' 'RcppArmadillo'
A package should be listed in only one of these fields.
* 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 ... NOTE
Packages in Depends field not imported from:
  'Rcpp' 'RcppArmadillo'
  These packages need to be imported from (in the NAMESPACE file)
  for when this namespace is loaded but not attached.
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... WARNING
Undocumented code objects:
  'data_base' 'data_subset' 'shrinking_cpp'
Undocumented data sets:
  'data_base' 'data_subset'
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 'plot_heatmap.Rd'
  'X'
Documented arguments not in \usage in Rd file 'plot_heatmap.Rd':
  'Matrix'

Undocumented arguments in Rd file 'precision_matrix.Rd'
  'X' 'dim' 'lam' 'shrink'
Documented arguments not in \usage in Rd file 'precision_matrix.Rd':
  'input' 'choose'

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 ... NOTE
Argument items with no description in Rd file 'precision_matrix.Rd':
  'min.eig'
* checking for unstated dependencies in examples ... OK
* checking contents of 'data' directory ... OK
* checking data for non-ASCII characters ... OK
* checking LazyData ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking compilation flags in Makevars ... OK
* checking for GNU extensions in Makefiles ... OK
* checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
* checking use of PKG_*FLAGS in Makefiles ... OK
* checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... OK
* checking compiled code ... OK
* checking examples ... OK
* checking PDF version of manual ... [14s] OK
* checking HTML version of manual ... OK
* DONE
Status: 2 WARNINGs, 5 NOTEs