CRAN Package Check Results for Maintainer ‘Sam Levin <levisc8 at gmail.com>’

Last updated on 2025-05-08 04:52:39 CEST.

Package ERROR NOTE OK
ipmr 13
Rpadrino 1 12
spind 2 11

Package ipmr

Current CRAN status: NOTE: 13

Version: 0.0.7
Check: Rd files
Result: NOTE checkRd: (-1) check_convergence.Rd:47: Lost braces 47 | \code{conv_plot}: code{ipm} invisibly. | ^ checkRd: (-1) init_ipm.Rd:50-51: Lost braces in \itemize; meant \describe ? checkRd: (-1) init_ipm.Rd:52-53: Lost braces in \itemize; meant \describe ? checkRd: (-1) init_ipm.Rd:57: Lost braces in \itemize; meant \describe ? checkRd: (-1) init_ipm.Rd:58: Lost braces in \itemize; meant \describe ? checkRd: (-1) init_ipm.Rd:62: Lost braces in \itemize; meant \describe ? checkRd: (-1) init_ipm.Rd:63-65: Lost braces in \itemize; meant \describe ? checkRd: (-1) init_ipm.Rd:70-74: Lost braces in \itemize; meant \describe ? checkRd: (-1) init_ipm.Rd:75-78: Lost braces in \itemize; meant \describe ? checkRd: (-1) make_ipm.Rd:276: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) make_ipm.Rd:277-281: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) make_ipm.Rd:282-286: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) make_ipm.Rd:287-291: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) make_ipm.Rd:292-293: 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, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Package Rpadrino

Current CRAN status: ERROR: 1, OK: 12

Version: 0.0.5
Check: re-building of vignette outputs
Result: ERROR Error(s) in re-building vignettes: ... --- re-building ‘data-cleaning.Rmd’ using rmarkdown --- finished re-building ‘data-cleaning.Rmd’ --- re-building ‘padrino-intro.Rmd’ using rmarkdown Quitting from padrino-intro.Rmd:22-29 [unnamed-chunk-1] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <error/rlang_error> Error in `open.connection()`: ! cannot open the connection to 'https://raw.githubusercontent.com/padrinoDB/Padrino/main/padrino-database/clean/ContinuousDomains.txt' --- Backtrace: ▆ 1. └─Rpadrino::pdb_download(save = FALSE) 2. └─utils::read.table(...) 3. ├─base::open(file, "rt") 4. └─base::open.connection(file, "rt") ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Error: processing vignette 'padrino-intro.Rmd' failed with diagnostics: cannot open the connection to 'https://raw.githubusercontent.com/padrinoDB/Padrino/main/padrino-database/clean/ContinuousDomains.txt' --- failed re-building ‘padrino-intro.Rmd’ --- re-building ‘pdb-msgs.Rmd’ using rmarkdown --- finished re-building ‘pdb-msgs.Rmd’ --- re-building ‘stoch-ipms.rmd’ using rmarkdown --- finished re-building ‘stoch-ipms.rmd’ SUMMARY: processing the following file failed: ‘padrino-intro.Rmd’ Error: Vignette re-building failed. Execution halted Flavor: r-devel-linux-x86_64-debian-gcc

Package spind

Current CRAN status: NOTE: 2, OK: 11

Version: 2.2.1
Check: CRAN incoming feasibility
Result: NOTE Maintainer: ‘Sam Levin <levisc8@gmail.com>’ No Authors@R field in DESCRIPTION. Please add one, modifying Authors@R: c(person(given = "Gudrun", family = "Carl", role = c("cre", "aut")), person(given = "Ingolf", family = "Kuehn", role = "aut"), person(given = "Sam", family = "Levin", role = c("aut", "cre"), email = "levisc8@gmail.com")) as necessary. Package CITATION file contains call(s) to old-style personList() or as.personList(). Please use c() on person objects instead. Package CITATION file contains call(s) to old-style citEntry(). Please use bibentry() instead. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-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.