The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

CRAN Package Check Results for Package sim2Dpredictr

Last updated on 2026-04-27 05:50:01 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.1.1 9.24 76.65 85.89 NOTE
r-devel-linux-x86_64-debian-gcc 0.1.1 5.50 54.46 59.96 NOTE
r-devel-linux-x86_64-fedora-clang 0.1.1 14.00 120.15 134.15 NOTE
r-devel-linux-x86_64-fedora-gcc 0.1.1 14.00 113.86 127.86 NOTE
r-patched-linux-x86_64 0.1.1 8.41 70.04 78.45 NOTE
r-release-linux-x86_64 0.1.1 8.05 70.42 78.47 NOTE
r-release-macos-arm64 0.1.1 2.00 19.00 21.00 NOTE
r-release-macos-x86_64 0.1.1 6.00 66.00 72.00 NOTE
r-release-windows-x86_64 0.1.1 11.00 88.00 99.00 NOTE
r-oldrel-macos-arm64 0.1.1 NOTE
r-oldrel-macos-x86_64 0.1.1 5.00 54.00 59.00 NOTE
r-oldrel-windows-x86_64 0.1.1 15.00 103.00 118.00 NOTE

Check Details

Version: 0.1.1
Check: CRAN incoming feasibility
Result: NOTE Maintainer: ‘Justin Leach <jleach@uab.edu>’ The BugReports field in DESCRIPTION has https://github.com/jmleach-bst/sim2Dpredictr which should likely be https://github.com/jmleach-bst/sim2Dpredictr/issues instead. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc

Version: 0.1.1
Check: Rd files
Result: NOTE checkRd: (-1) sim_Y_Binary_X.Rd:51: Lost braces 51 | \item \code{dist = "binomial"} is drawn from eqn{Bin(XB, XB(1-XB))} | ^ 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, 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

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.