===============================
R CMD BUILD
===============================
* checking for file ‘Yeskit/DESCRIPTION’ ... OK
* preparing ‘Yeskit’:
* checking DESCRIPTION meta-information ... OK
* installing the package to build vignettes
* creating vignettes ... OK
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
* building ‘Yeskit_0.99.0.tar.gz’
===============================
BiocCheckGitClone('Yeskit')
===============================
This is BiocCheckGitClone version 1.29.14. BiocCheckGitClone is a work
in progress. Output and severity of issues may change.
* Checking valid files...
* Checking DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for valid maintainer...
* Checking CITATION...
Summary:
ERROR count: 0
WARNING count: 0
NOTE count: 0
For detailed information about these checks, see the BiocCheck
vignette, available at
https://bioconductor.org/packages/3.14/bioc/vignettes/BiocCheck/inst/doc/BiocCheck.html#interpreting-bioccheck-output
===============================
R CMD CHECK
===============================
* using log directory ‘/home/pkgbuild/packagebuilder/workers/jobs/2378/Yeskit_20211004173819/Yeskit.Rcheck’
* using R version 4.1.1 (2021-08-10)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘Yeskit/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘Yeskit’ version ‘0.99.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 for sufficient/correct file permissions ... OK
* checking whether package ‘Yeskit’ can be installed ... [22s/22s] OK
* checking installed package size ... NOTE
installed size is 6.1Mb
sub-directories of 1Mb or more:
data 1.7Mb
doc 2.2Mb
extdata 1.9Mb
* 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 R 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 ... [23s/23s] OK
* checking Rd files ... [0s/0s] 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 ... OK
* 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 LazyData ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [314s/308s] OK
Examples with CPU (user + system) or elapsed time > 5s
user system elapsed
scPathogenGO 105.649 2.616 108.268
scGO 102.245 1.668 103.916
scDGE 28.952 0.567 26.080
scPathogenDGE 28.795 0.176 25.964
scIntegrate 10.386 0.172 10.558
scOne 7.620 0.032 7.653
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in ‘inst/doc’ ... OK
* checking running R code from vignettes ... SKIPPED
* checking re-building of vignette outputs ... SKIPPED
* checking PDF version of manual ... OK
* DONE
Status: 1 NOTE
See
‘/home/pkgbuild/packagebuilder/workers/jobs/2378/Yeskit_20211004173819/Yeskit.Rcheck/00check.log’
for details.
===============================
BiocCheck('Yeskit_0.99.0.tar.gz')
===============================
This is BiocCheck version 1.29.14. BiocCheck is a work in progress.
Output and severity of issues may change. Installing package...
* Checking Package Dependencies...
* Checking if other packages can import this one...
* Checking to see if we understand object initialization...
* Checking for deprecated package usage...
* Checking for remote package usage...
* Checking for 'LazyData: true' usage...
* NOTE: 'LazyData:' in the 'DESCRIPTION' should be set to false or
removed
* Checking version number...
* Checking for version number mismatch...
* Checking new package version number...
* Checking R Version dependency...
* NOTE: Update R version dependency from 3.6.0 to 4.1.0.
* Checking package size...
* Checking individual file sizes...
* Checking biocViews...
* Checking that biocViews are present...
* Checking package type based on biocViews...
Software
* Checking for non-trivial biocViews...
* Checking that biocViews come from the same category...
* Checking biocViews validity...
* Checking for recommended biocViews...
* Checking build system compatibility...
* Checking for blank lines in DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for proper Description: field...
* Checking for whitespace in DESCRIPTION field names...
* Checking that Package field matches directory/tarball name...
* Checking for Version field...
* Checking for valid maintainer...
* Checking License: for restrictive use...
* Checking DESCRIPTION/NAMESPACE consistency...
* Checking .Rbuildignore...
* Checking vignette directory...
* Checking whether vignette is built with 'R CMD build'...
* Checking package installation calls in R code...
* Checking for library/require of Yeskit...
* Checking coding practice...
* Checking parsed R code in R directory, examples, vignettes...
* NOTE: Avoid 'suppressWarnings'/'*Messages' if possible (found 9
times)
suppressWarnings() in R/scDGE.R (line 69, column 14)
suppressMessages() in R/scGO.R (line 111, column 19)
suppressMessages() in R/scGO.R (line 114, column 29)
suppressWarnings() in R/scPathogenDGE.R (line 70, column 9)
suppressMessages() in R/scPathogenDGE.R (line 69, column 16)
suppressMessages() in R/scPathogenGO.R (line 122, column 19)
suppressMessages() in R/scPathogenGO.R (line 126, column 29)
suppressWarnings() in R/scScoreDimPlot.R (line 70, column 13)
suppressWarnings() in R/scScoreDimPlot.R (line 99, column 13)
* Checking function lengths.....................................
* NOTE: Recommended function length <= 50 lines.
There are 15 functions > 50 lines.
The longest 5 functions are:
scDimPlot() (R/scDimPlot.R, line 42): 159 lines
scVizMeta() (R/scVizMeta.R, line 44): 154 lines
scScoreDimPlot() (R/scScoreDimPlot.R, line 41): 139 lines
scGODotPlot() (R/scGODotPlot.R, line 34): 120 lines
scVolcanoPlot() (R/scVolcanoPlot.R, line 36): 112 lines
* Checking man page documentation...
* Checking package NEWS...
* Checking unit tests...
* NOTE: Consider adding unit tests. We strongly encourage them. See
http://bioconductor.org/developers/how-to/unitTesting-guidelines/.
* Checking skip_on_bioc() in tests...
* Checking formatting of DESCRIPTION, NAMESPACE, man pages, R source,
and vignette source...
* NOTE: Consider multiples of 4 spaces for line indents, 1171
lines(32%) are not.
First 6 lines:
R/scDensityPlot.R:33 split.by = NULL, ncol = ...
R/scDensityPlot.R:34 digits = NULL) {
R/scDensityPlot.R:35 if (is.null(reduction)) {
R/scDensityPlot.R:37 reduction <- "umap"
R/scDensityPlot.R:39 reduction <- "tsne"
R/scDensityPlot.R:41 reduction <- "pca"
See http://bioconductor.org/developers/how-to/coding-style/
See styler package: https://cran.r-project.org/package=styler as
described in the BiocCheck vignette.
* Checking if package already exists in CRAN...
* Checking if new package already exists in Bioconductor...
* Checking for bioc-devel mailing list subscription...
Maintainer is subscribed to bioc-devel.
* Checking for support site registration...
Maintainer is registered at support site.
Package name is in support site watched tags.
Summary:
ERROR count: 0
WARNING count: 0
NOTE count: 6
For detailed information about these checks, see the BiocCheck
vignette, available at
https://bioconductor.org/packages/3.14/bioc/vignettes/BiocCheck/inst/doc/BiocCheck.html#interpreting-bioccheck-output