* using log directory 'd:/RCompile/CRANincoming/R-devel/autotune.Rcheck' * using R Under development (unstable) (2026-07-24 r90297 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 14.3.0 GNU Fortran (GCC) 14.3.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * current time: 2026-07-25 17:00:32 UTC * checking for file 'autotune/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'autotune' version '0.1.0' * package encoding: UTF-8 * checking CRAN incoming feasibility ... NOTE Maintainer: 'Tathagata Sadhukhan ' New submission Possibly misspelled words in DESCRIPTION: autotune (7:158) glmnet (3:46, 7:206) scalreg (3:57) The Title field should be in title case. Current version is: 'Faster and more efficient Lasso (than glmnet and scalreg) with data-driven tuning' In title case that is: 'Faster and more Efficient Lasso (than Glmnet and Scalreg) with Data-Driven Tuning' The Description field should not start with the package name, 'This package' or similar. * 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 'autotune' can be installed ... OK * used C++ compiler: 'g++.exe (GCC) 14.3.0' * checking installed package size ... OK * checking package directory ... OK * checking for future file timestamps ... OK * checking 'build' directory ... 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 ... WARNING plot: function(x, ...) plot.autotune_lasso: function(object, max_preds, cumulative, ...) See section 'Generic functions and methods' in the 'Writing R Extensions' manual. * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... OK * checking Rd files ... NOTE checkRd: (-1) autotune_lasso.Rd:89-90: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) autotune_lasso.Rd:91-92: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) autotune_lasso.Rd:93-94: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) autotune_lasso.Rd:95-96: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) autotune_lasso.Rd:97-99: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) autotune_lasso.Rd:100: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) autotune_lasso.Rd:101-102: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) autotune_lasso.Rd:103-104: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) autotune_lasso.Rd:105-107: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) autotune_lasso.Rd:108-111: Lost braces 108 | \item{\code{null_support:}{ Boolean output indicating whether final estimate of | ^ * checking Rd metadata ... OK * checking Rd line widths ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... WARNING Undocumented code objects: 'autotune_lasso_cpp' 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 ... WARNING Codoc mismatches from Rd file 'autotune_lasso.Rd': autotune_lasso Code: function(x, y, ...) Docs: function(x, y, alpha = 0.01, standardize = TRUE, standardize_response = TRUE, intercept = TRUE, active = FALSE, trace_it = FALSE, tolerance = 1e-04, beta_tolerance = 0.001, iter_max = 30, beta_iter_max = 40, active_iter_max = 5, PR_norm_l2 = FALSE) Argument names in code not in docs: ... Argument names in docs not in code: alpha standardize standardize_response intercept active trace_it tolerance beta_tolerance iter_max beta_iter_max active_iter_max PR_norm_l2 Mismatches in argument names: Position: 3 Code: ... Docs: alpha * checking Rd \usage sections ... WARNING Undocumented arguments in Rd file 'predict.autotune_lasso.Rd' 'path' 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 ... OK * checking for unstated dependencies in examples ... OK * checking contents of 'data' directory ... OK * checking data for non-ASCII characters ... OK * checking data for ASCII and uncompressed saves ... OK * checking line endings in C/C++/Fortran sources/headers ... OK * checking pragmas in C/C++ headers and code ... OK * checking compilation flags used ... OK * checking compiled code ... OK * checking installed files from 'inst/doc' ... OK * checking files in 'vignettes' ... OK * checking examples ... OK * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... [11s] OK * checking PDF version of manual ... [12s] OK * checking HTML version of manual ... OK * DONE Status: 4 WARNINGs, 2 NOTEs