CRAN Package Check Results for Maintainer ‘Ewoud De Troyer <ewoud.detroyer at uhasselt.be>’

Last updated on 2024-11-21 19:53:07 CET.

Package WARN NOTE OK
BcDiag 6 7
BiBitR 13
RcmdrPlugin.BiclustGUI 2 9 2

Package BcDiag

Current CRAN status: NOTE: 6, OK: 7

Version: 1.0.10
Check: for non-standard things in the check directory
Result: NOTE Found the following files/directories: ‘fabiabreast.txt’ 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-patched-linux-x86_64, r-release-linux-x86_64

Package BiBitR

Current CRAN status: OK: 13

Package RcmdrPlugin.BiclustGUI

Current CRAN status: WARN: 2, NOTE: 9, OK: 2

Version: 1.1.3.1
Check: whether startup messages can be suppressed
Result: NOTE Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified It looks like this package (or a package it requires) has a startup message which cannot be suppressed: see ?packageStartupMessage. Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.1.3.1
Check: dependencies in R code
Result: NOTE Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.1.3.1
Check: S3 generic/method consistency
Result: WARN Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified See section ‘Generic functions and methods’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.1.3.1
Check: replacement functions
Result: WARN Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified The argument of a replacement function which corresponds to the right hand side must be named ‘value’. Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.1.3.1
Check: foreign function calls
Result: NOTE Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified See chapter ‘System and foreign language interfaces’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.1.3.1
Check: R code for possible problems
Result: NOTE Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.1.3.1
Check: Rd cross-references
Result: NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors: BiclustGUI.Rd: biclust, fabia, iBBiG, BicARE, superbiclust, BcDiag-package Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64

Version: 1.1.3.1
Check: for missing documentation entries
Result: WARN Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified All user-level objects in a package should have documentation entries. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.1.3.1
Check: for code/documentation mismatches
Result: WARN Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.1.3.1
Check: Rd \usage sections
Result: NOTE Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified 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. Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.1.3.1
Check: package dependencies
Result: NOTE Depends: includes the non-default packages: 'biclust', 'fabia', 'iBBiG', 'superbiclust', 'BcDiag', 'BicARE', 's4vd', 'BiBitR' Adding so many packages to the search path is excessive and importing selectively is preferable. Flavors: r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-windows-x86_64

Version: 1.1.3.1
Check: re-building of vignette outputs
Result: WARN Error(s) in re-building vignettes: ... --- re-building ‘GuideBiclustGUI.Rnw’ using knitr Error: processing vignette 'GuideBiclustGUI.Rnw' failed with diagnostics: Running 'texi2dvi' on 'GuideBiclustGUI.tex' failed. LaTeX errors: ! Undefined control sequence. l.2365 \hldef {newmethod_WINDOW} \hlkwb{<-} \hlkwa{function}\hldef{()\{} ? ! Emergency stop. ! Emergency stop. l.2365 End of file on the terminal! ! ==> Fatal error occurred, no output PDF file produced! --- failed re-building ‘GuideBiclustGUI.Rnw’ SUMMARY: processing the following file failed: ‘GuideBiclustGUI.Rnw’ Error: Vignette re-building failed. Execution halted Flavor: r-release-macos-x86_64

Version: 1.1.3.1
Check: package dependencies
Result: NOTE Package suggested but not available for checking: ‘rqubic’ Depends: includes the non-default packages: 'biclust', 'fabia', 'iBBiG', 'superbiclust', 'BcDiag', 'BicARE', 's4vd', 'BiBitR' Adding so many packages to the search path is excessive and importing selectively is preferable. Flavors: r-oldrel-macos-arm64, r-oldrel-macos-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.