CRAN Package Check Results for Maintainer ‘B. W. Lewis <blewis at illposed.net>’

Last updated on 2024-05-02 09:52:29 CEST.

Package ERROR NOTE OK
doRedis 9 3
irlba 1 9 2
threejs 9 3

Package doRedis

Current CRAN status: NOTE: 9, OK: 3

Version: 3.0.2
Check: Rd files
Result: NOTE checkRd: (-1) redisWorker.Rd:56: Lost braces; missing escapes or markup? 56 | You can increase it by including a {timeout=n} argument value. | ^ checkRd: (-1) startLocalWorkers.Rd:54: Lost braces; missing escapes or markup? 54 | You can increase it by including a {timeout=n} argument value. | ^ Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-windows-x86_64

Package irlba

Current CRAN status: ERROR: 1, NOTE: 9, OK: 2

Version: 2.3.5.1
Check: Rd files
Result: NOTE checkRd: (-1) partial_eigen.Rd:23: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) partial_eigen.Rd:24: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) prcomp_irlba.Rd:41-44: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) prcomp_irlba.Rd:45-46: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) prcomp_irlba.Rd:47-50: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) prcomp_irlba.Rd:51: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) ssvd.Rd:52: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) ssvd.Rd:53: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) ssvd.Rd:54: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) ssvd.Rd:55: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) ssvd.Rd:56: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) ssvd.Rd:57: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) ssvd.Rd:58: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) ssvd.Rd:59: Lost braces in \itemize; \value handles \item{}{} directly Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-windows-x86_64

Version: 2.3.5.1
Check: tests
Result: ERROR Running ‘edge.R’ [1s/1s] Running ‘prcomp.r’ [1s/1s] Running ‘ssvd.R’ [1s/1s] Running ‘svdr.R’ [1s/1s] Running ‘test.R’ [1s/1s] Running the tests in ‘tests/test.R’ failed. Last 13 lines of output: + + # test for https://github.com/bwlewis/irlba/issues/42 + set.seed(1234) + a <- matrix(rnorm(10000), ncol=20) + center <- runif(ncol(a)) + scale <- runif(ncol(a)) + L <- irlba(a, 5, scale=scale, center=center, fastpath=FAST) + S <- svd(scale(a, center=center, scale=scale)) + if (isTRUE(max(abs(S$d[1:5] - L$d)) > 1e-3)) + { + stop("Failed scale + center test fastpath=", FAST) + } + } Error: Failed tprolate test fastpath=FALSE Execution halted Flavor: r-oldrel-macos-arm64

Package threejs

Current CRAN status: NOTE: 9, OK: 3

Version: 0.3.3
Check: Rd files
Result: NOTE checkRd: (-1) globejs.Rd:88: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:89: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:90: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:91: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:92: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:93: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:94: Lost braces in \itemize; meant \describe ? checkRd: (-1) globejs.Rd:95-98: Lost braces in \itemize; meant \describe ? checkRd: (-1) graphjs.Rd:139-140: Lost braces in \itemize; meant \describe ? checkRd: (-1) graphjs.Rd:141: Lost braces in \itemize; meant \describe ? checkRd: (-1) graphjs.Rd:142: Lost braces in \itemize; meant \describe ? checkRd: (-1) graphjs.Rd:143: Lost braces in \itemize; meant \describe ? checkRd: (-1) graphjs.Rd:144-145: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:149: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:150: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:151: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:152: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:153: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:154: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:155: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:156: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:157: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:158: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:169: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:170: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:171: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:174: Lost braces; missing escapes or markup? 174 | The \code{@} and {.} option exhibit the best performance, consider using | ^ checkRd: (-1) scatterplot3js.Rd:187: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:188-189: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:190-191: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:192: Lost braces in \itemize; meant \describe ? checkRd: (-1) scatterplot3js.Rd:193-194: Lost braces in \itemize; meant \describe ? Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-windows-x86_64

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.