CRAN Package Check Results for Package LEGIT

Last updated on 2023-11-28 16:48:23 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.4.0 12.67 325.34 338.01 NOTE
r-devel-linux-x86_64-debian-gcc 1.4.0 10.15 238.72 248.87 NOTE
r-devel-linux-x86_64-fedora-clang 1.4.0 396.60 NOTE
r-devel-linux-x86_64-fedora-gcc 1.4.0 401.78 NOTE
r-devel-windows-x86_64 1.4.0 11.00 228.00 239.00 NOTE
r-patched-linux-x86_64 1.4.0 11.58 300.62 312.20 OK
r-release-linux-x86_64 1.4.0 8.22 303.18 311.40 OK
r-release-macos-arm64 1.4.0 135.00 OK
r-release-macos-x86_64 1.4.0 222.00 OK
r-release-windows-x86_64 1.4.0 15.00 306.00 321.00 OK
r-oldrel-macos-arm64 1.4.0 112.00 OK
r-oldrel-macos-x86_64 1.4.0 177.00 OK
r-oldrel-windows-x86_64 1.4.0 16.00 313.00 329.00 OK

Check Details

Version: 1.4.0
Check: Rd \usage sections
Result: NOTE Documented arguments not in \usage in Rd file 'backward_step.Rd': ‘empty_start_dataset’ ‘fit’ ‘...’ Documented arguments not in \usage in Rd file 'backward_step_IM.Rd': ‘empty_start_dataset’ ‘fit’ ‘...’ Documented arguments not in \usage in Rd file 'forward_step.Rd': ‘empty_start_dataset’ ‘fit’ ‘...’ Documented arguments not in \usage in Rd file 'forward_step_IM.Rd': ‘empty_start_dataset’ ‘fit’ ‘...’ Functions with \usage entries need to have the appropriate \alias entries, and all their arguments documented. The \usage entries must correspond to syntactically valid R code. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. 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