############################################################################## ############################################################################## ### ### Running command: ### ### E:\biocbuild\bbs-3.21-bioc\R\bin\R.exe CMD check --no-multiarch --install=check:blima.install-out.txt --library=E:\biocbuild\bbs-3.21-bioc\R\library --no-vignettes --timings blima_1.41.0.tar.gz ### ############################################################################## ############################################################################## * using log directory 'E:/biocbuild/bbs-3.21-bioc/meat/blima.Rcheck' * using R Under development (unstable) (2024-10-26 r87273 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 * using option '--no-vignettes' * checking for file 'blima/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'blima' version '1.41.0' * package encoding: UTF-8 * 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 whether package 'blima' can be installed ... OK * used C++ compiler: 'G__~1.EXE (GCC) 13.3.0' * checking installed package size ... OK * checking package directory ... 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 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 ... NOTE nonParametricEstimator: no visible global function definition for 'var' performXieCorrection: no visible global function definition for 'dnorm' performXieCorrection: no visible global function definition for 'pnorm' vstFromLumi: no visible global function definition for 'lm' vstFromLumi: no visible global function definition for 'predict' Undefined global functions or variables: dnorm lm pnorm predict var Consider adding importFrom("stats", "dnorm", "lm", "pnorm", "predict", "var") to your NAMESPACE file. * checking Rd files ... NOTE checkRd: (-1) createSummarizedMatrix.Rd:11: Lost braces; missing escapes or markup? 11 | \item{channelInclude}{This field allows user to set channel with weights which have to be from {0,1}. | ^ checkRd: (-1) doProbeTTests.Rd:12: Lost braces; missing escapes or markup? 12 | \item{channelInclude}{This field allows user to set channel with weights which have to be {0,1}. | ^ checkRd: (-1) doTTests.Rd:12: Lost braces; missing escapes or markup? 12 | \item{channelInclude}{This field allows user to set channel with weights which have to be {0,1}. | ^ checkRd: (-1) meanDistribution.Rd:15: Lost braces; missing escapes or markup? 15 | \item{channelInclude}{This field allows user to set channel with weights which have to be in {0,1}. | ^ checkRd: (-1) quantileNormalize.Rd:12: Lost braces; missing escapes or markup? 12 | \item{channelInclude}{This field allows user to set channel with weights which have to be in {0,1}. | ^ checkRd: (-1) singleArrayNormalize.Rd:13: Lost braces; missing escapes or markup? 13 | \item{channelInclude}{This field allows user to set channel with weights which have to be in {0,1}. | ^ checkRd: (-1) varianceBeadStabilise.Rd:11: Lost braces; missing escapes or markup? 11 | \item{channelInclude}{This field allows user to set channel with weights which have to be in {0,1}. | ^ checkRd: (-1) varianceBeadStabiliseSingleArray.Rd:11: Lost braces; missing escapes or markup? 11 | \item{channelInclude}{This field allows user to set channel with weights which have to be in {0,1}. | ^ checkRd: (-1) xieBacgroundCorrect.Rd:16: Lost braces; missing escapes or markup? 16 | \item{channelInclude}{This field allows user to set channel with weights which have to be from {0,1}. | ^ checkRd: (-1) xieBacgroundCorrectSingleArray.Rd:18: Lost braces; missing escapes or markup? 18 | \item{channelInclude}{This field allows user to set channel with weights which have to be from {0,1}. | ^ * checking Rd metadata ... OK * 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 ... NOTE Rd files without \description: 'interpolateSortedVectorRcpp_.Rd' Argument items with no description in Rd file 'interpolateSortedVectorRcpp_.Rd': 'vector' 'newSize' Argument items with no description in Rd file 'nonParametricEstimator.Rd': 'toCorrectAll' 'toCorrectNeg' Argument items with no description in Rd file 'numberOfDistributionElements.Rd': 'channelInclude' Argument items with no description in Rd file 'performXieCorrection.Rd': 'value' 'alpha' 'mu' 'sigma' Argument items with no description in Rd file 'singleNumberOfDistributionElements.Rd': 'channelInclude' Argument items with no description in Rd file 'updateMeanDistribution.Rd': 'meanDistribution' * checking for unstated dependencies in examples ... OK * checking line endings in C/C++/Fortran sources/headers ... OK * checking compiled code ... NOTE Note: information on .o files for x64 is not available File 'E:/biocbuild/bbs-3.21-bioc/R/library/blima/libs/x64/blima.dll': Found '_exit', possibly from '_exit' (C) Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran) Found 'exit', possibly from 'exit' (C), 'stop' (Fortran) Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs nor [v]sprintf. The detected symbols are linked into the code but might come from libraries and not actually be called. See 'Writing portable packages' in the 'Writing R Extensions' manual. * checking sizes of PDF files under 'inst/doc' ... OK * checking files in 'vignettes' ... OK * checking examples ... OK * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking running R code from vignettes ... SKIPPED * checking re-building of vignette outputs ... SKIPPED * checking PDF version of manual ... OK * DONE Status: 4 NOTEs See 'E:/biocbuild/bbs-3.21-bioc/meat/blima.Rcheck/00check.log' for details.