* using log directory 'd:/RCompile/CRANincoming/R-devel/CP2I.Rcheck' * using R Under development (unstable) (2024-10-22 r87265 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 'CP2I/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'CP2I' version '0.1.0' * package encoding: UTF-8 * checking CRAN incoming feasibility ... NOTE Maintainer: 'Yanxi Liu ' New submission Possibly misspelled words in DESCRIPTION: Liu (10:123) Safikhani (10:131) Package has a VignetteBuilder field but no prebuilt vignette index. The Title field should be in title case. Current version is: 'Change Point Detection with Data Missing Not At Random' In title case that is: 'Change Point Detection with Data Missing not at Random' * checking package namespace information ... OK * checking package dependencies ... INFO Vignette dependency required without any vignettes: 'knitr' * 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 'CP2I' 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 ... 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 ... 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 ... [11s] OK * checking Rd files ... OK * checking Rd metadata ... OK * checking Rd line widths ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... NOTE S3 methods shown with full name in Rd file 'BIC.threshold.Rd': 'BIC.threshold' The \usage entries for S3 methods should use the \method markup and not their full name. See chapter 'Writing R documentation files' in the 'Writing R Extensions' manual. * checking Rd contents ... OK * checking for unstated dependencies in examples ... 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 ... [313s] NOTE Examples with CPU (user + system) or elapsed time > 10s user system elapsed CP2I 220.86 89.18 310.03 * checking PDF version of manual ... [20s] OK * checking HTML version of manual ... OK * DONE Status: 3 NOTEs