CRAN Package Check Results for Maintainer ‘Eunseop Kim <markean at pm.me>’

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

Package WARN NOTE OK
elgbd 4 9
melt 1 3 9
retel 3 10

Package elgbd

Current CRAN status: NOTE: 4, OK: 9

Version: 0.9.0
Check: installed package size
Result: NOTE installed size is 39.2Mb sub-directories of 1Mb or more: libs 39.1Mb Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Package melt

Current CRAN status: WARN: 1, NOTE: 3, OK: 9

Version: 1.11.4
Check: installed package size
Result: NOTE installed size is 155.5Mb sub-directories of 1Mb or more: libs 154.0Mb Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Version: 1.11.4
Check: re-building of vignette outputs
Result: WARN Error(s) in re-building vignettes: --- re-building ‘model.Rmd’ using rmarkdown --- finished re-building ‘model.Rmd’ --- re-building ‘performance.Rmd’ using rmarkdown --- finished re-building ‘performance.Rmd’ --- re-building ‘article.Rnw’ using knitr Error: processing vignette 'article.Rnw' failed with diagnostics: Running 'texi2dvi' on 'article.tex' failed. LaTeX errors: ! Undefined control sequence. l.914 \hlkwd{library}\hldef {(}\hlsng{"melt"}\hldef{)} ? ! Emergency stop. ! Emergency stop. l.914 End of file on the terminal! ! ==> Fatal error occurred, no output PDF file produced! --- failed re-building ‘article.Rnw’ SUMMARY: processing the following file failed: ‘article.Rnw’ Error: Vignette re-building failed. Execution halted Flavor: r-release-macos-x86_64

Package retel

Current CRAN status: NOTE: 3, OK: 10

Version: 0.1.0
Check: Rd cross-references
Result: NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors: etel.Rd: nloptr retel.Rd: nloptr 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

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.