CRAN Package Check Results for Maintainer ‘Yasuhiro Sato <sato.yasuhiro.36c at kyoto-u.jp>’

Last updated on 2024-12-22 13:49:20 CET.

Package NOTE OK
rNeighborGWAS 10 3
rNeighborQTL 10 3

Package rNeighborGWAS

Current CRAN status: NOTE: 10, OK: 3

Version: 1.2.4
Check: Rd files
Result: NOTE checkRd: (-1) calc_PVEnei.Rd:38: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) calc_PVEnei.Rd:39: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) calc_PVEnei.Rd:40: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) calc_PVEnei.Rd:41: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) gaston2neiGWAS.Rd:15: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) gaston2neiGWAS.Rd:16: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) gaston2neiGWAS.Rd:17: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) neiGWAS.Rd:44: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) neiGWAS.Rd:45: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) neiGWAS.Rd:46: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) nei_lm.Rd:35: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) nei_lm.Rd:36: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) nei_lm.Rd:37: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) nei_lm.Rd:38: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) nei_lmm.Rd:35: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) nei_lmm.Rd:36: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) nei_lmm.Rd:37: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) nei_lmm.Rd:38: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) qtl_pheno_simu.Rd:35: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) qtl_pheno_simu.Rd:36: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) qtl_pheno_simu.Rd:37: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) qtl_pheno_simu.Rd:38: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) qtl_pheno_simu.Rd:39: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) qtl_pheno_simu.Rd:40: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) qtl_pheno_simu.Rd:41: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) qtl_pheno_simu.Rd:42: 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-macos-x86_64, r-release-windows-x86_64

Version: 1.2.4
Check: Rd cross-references
Result: NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors: gaston2neiGWAS.Rd: gaston, bed.matrix 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

Package rNeighborQTL

Current CRAN status: NOTE: 10, OK: 3

Version: 1.1.2
Check: Rd files
Result: NOTE checkRd: (-1) calc_pve.Rd:41: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) calc_pve.Rd:42: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) calc_pve.Rd:43: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) calc_pve.Rd:44: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) decompose_genoprobs.Rd:17: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) decompose_genoprobs.Rd:18: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) decompose_genoprobs.Rd:19: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) eff_neighbor.Rd:44: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) eff_neighbor.Rd:45: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) eff_neighbor.Rd:46: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) eff_neighbor.Rd:47: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) eff_neighbor.Rd:48: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) eff_neighbor.Rd:49: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) int_neighbor.Rd:44: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) int_neighbor.Rd:45: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) int_neighbor.Rd:46: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) scan_neighbor.Rd:41: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) scan_neighbor.Rd:42: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) scan_neighbor.Rd:43: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) scan_neighbor.Rd:44: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) sim_nei_qtl.Rd:38: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) sim_nei_qtl.Rd:39: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) sim_nei_qtl.Rd:40: 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-macos-x86_64, r-release-windows-x86_64

Version: 1.1.2
Check: dependencies in R code
Result: NOTE Namespace in Imports field not imported from: ‘qtl’ All declared Imports should be used. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

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.