* using log directory 'd:/RCompile/CRANincoming/R-devel/binr.Rcheck' * using R Under development (unstable) (2026-02-02 r89367 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-02-03 21:48:02Z * checking for file 'binr/DESCRIPTION' ... OK * this is package 'binr' version '1.2.1' * package encoding: UTF-8 * checking CRAN incoming feasibility ... NOTE Maintainer: 'Sergei Izrailev ' Possibly misspelled words in DESCRIPTION: binner (8:43) binr (8:22) * 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 'binr' can be installed ... OK * 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 ... NOTE Mismatches for apparent methods not registered: bins: function(x, ...) bins.move.iter: function(lst, target.bins, verbose) bins: function(x, ...) bins.move: function(xval, xtbl, binlo, binhi, binct, target.bins, verbose) bins: function(x, ...) bins.quantiles: function(x, target.bins, max.breaks, verbose) bins: function(x, ...) bins.split: function(xval, xtbl, binlo, binhi, binct, target.bins, force, verbose) bins: function(x, ...) bins.greedy: function(x, nbins, minpts, thresh, naive) bins: function(x, ...) bins.split.iter: function(lst, target.bins, exact.groups, verbose) bins: function(x, ...) bins.merge.iter: function(lst, target.bins, exact.groups, verbose) bins: function(x, ...) bins.merge: function(xval, xtbl, binlo, binhi, binct, target.bins, force, verbose) bins: function(x, ...) bins.getvals: function(lst, minpt, maxpt) bins: function(x, ...) bins.greedy.impl: function(xval, xtbl, xstp, binsz, nbins, thresh, verbose) bins: function(x, ...) bins.merr: function(binct, target.bins) Apparent methods for exported generics not registered: bins.getvals bins.greedy bins.greedy.impl bins.merge bins.merge.iter bins.merr bins.move bins.move.iter bins.quantiles bins.split bins.split.iter See section 'Registering S3 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 ... 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 'bins.getvals.Rd': 'bins.getvals' S3 methods shown with full name in Rd file 'bins.greedy.Rd': 'bins.greedy' 'bins.greedy.impl' S3 methods shown with full name in Rd file 'bins.merr.Rd': 'bins.merr' S3 methods shown with full name in Rd file 'bins.optimize.Rd': 'bins.move' 'bins.split' 'bins.merge' 'bins.move.iter' 'bins.split.iter' 'bins.merge.iter' S3 methods shown with full name in Rd file 'bins.quantiles.Rd': 'bins.quantiles' 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 examples ... OK * checking PDF version of manual ... [12s] OK * checking HTML version of manual ... OK * DONE Status: 3 NOTEs