CRAN Package Check Results for Package ctmm

Last updated on 2024-07-23 07:07:11 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.2.0 81.44 726.90 808.34 NOTE --no-vignettes
r-devel-linux-x86_64-debian-gcc 1.2.0 58.51 533.03 591.54 NOTE --no-vignettes
r-devel-linux-x86_64-fedora-clang 1.2.0 1005.83 NOTE --no-vignettes
r-devel-linux-x86_64-fedora-gcc 1.2.0 924.85 NOTE --no-vignettes
r-devel-windows-x86_64 1.2.0 133.00 648.00 781.00 NOTE --no-vignettes
r-patched-linux-x86_64 1.2.0 82.19 680.29 762.48 NOTE --no-vignettes
r-release-linux-x86_64 1.2.0 66.08 693.64 759.72 NOTE --no-vignettes
r-release-macos-arm64 1.2.0 1803.00 NOTE
r-release-macos-x86_64 1.2.0 1803.00 NOTE
r-release-windows-x86_64 1.2.0 127.00 650.00 777.00 NOTE --no-vignettes
r-oldrel-macos-arm64 1.2.0 1803.00 OK
r-oldrel-macos-x86_64 1.2.0 1803.00 OK
r-oldrel-windows-x86_64 1.2.0 137.00 606.00 743.00 OK --no-vignettes

Check Details

Version: 1.2.0
Flags: --no-vignettes
Check: Rd files
Result: NOTE checkRd: (-1) ctmm-FAQ.Rd:28-30: Lost braces 28 | {These are the packages I needed in Ubuntu: | ^ checkRd: (-1) ctmm-FAQ.Rd:34: Lost braces 34 | {Make sure that you have the correct \code{timezone} and \code{timeformat} arguments specified. Also, see \code{\link{outlie}}.} | ^ checkRd: (-1) ctmm-FAQ.Rd:38: Lost braces 38 | {\code{R} might not have installed or loaded the package correctly---e.g., some files may have failed to overwrite previous versions---or the workspace/session might be corrupted. Uninstall \code{ctmm}, restart \code{R} without saving the workspace/session, and install \code{ctmm} again.} | ^ checkRd: (-1) ctmm-FAQ.Rd:43-48: Lost braces 43 | {\code{ctmm} has no recursive functions, so I am not exactly sure what causes this error, but it only occurs with certain versions of \code{R} on certain computer architectures. There are several solutions that have worked for people, including restarting \code{R} in a fresh session and updating their software. Alternatively: | ^ checkRd: (-1) ctmm-FAQ.Rd:52: Lost braces 52 | {Namespace collision sometimes occurs between \code{raster}, \code{sp}, \code{move}, and \code{ctmm}. Either restart \code{R} and only load the \code{ctmm} package, or run \code{ctmm::plot} instead of \code{plot}.} | ^ checkRd: (-1) ctmm-FAQ.Rd:56: Lost braces 56 | {The default projection in \code{ctmm} does not preserve the direction of North, but better preserves distances for elongated distributions. See the \code{projection} argument in \code{\link{as.telemetry}} and the example in \code{\link[ctmm]{projection}}. The \code{\link{compass}} function is also useful for pointing north.} | ^ checkRd: (-1) ctmm-FAQ.Rd:60: Lost braces 60 | {Namespace collision can occur between \code{raster} and \code{ctmm}. Either restart \code{R} and only load the \code{ctmm} package, or run \code{ctmm::projection} instead of \code{projection}.} | ^ checkRd: (-1) ctmm-FAQ.Rd:64: Lost braces; missing escapes or markup? 64 | {Maximize the plot window and/or increase your screen resolution.} | ^ checkRd: (-1) ctmm-FAQ.Rd:68: Lost braces; missing escapes or markup? 68 | {Click the gear icon in the upper-left corner of the plot window.} | ^ checkRd: (-1) ctmm-FAQ.Rd:72: Lost braces 72 | {Recent versions of \code{manipulate} and/or RStudio seem to have some issues. Sometimes the gear icon does not render unless you re-run the function 2-5 times.} | ^ checkRd: (-1) ctmm-FAQ.Rd:76: Lost braces 76 | {You probably have an outdated copy of the \code{manipulate} package installed. Update \code{R} to the latest version and then update all of your packages. This seems to happen frequently with the MacOS release of \code{R}.} | ^ checkRd: (-1) sigfig.Rd:20: Lost braces; missing escapes or markup? 20 | \item{est}{Can be either confidence-interval estimates with rows {(lower-limit,point-estimate,upper-limit)} or point estimates (with \code{VAR} or \code{SD} also specified).} | ^ 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-windows-x86_64

Version: 1.2.0
Flags: --no-vignettes
Check: Rd cross-references
Result: NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors: akde.Rd: res as.telemetry.Rd: fread ctmm-FAQ.Rd: zoom projection.Rd: CRS 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-gcc, r-devel-windows-x86_64

Version: 1.2.0
Check: Rd files
Result: NOTE checkRd: (-1) ctmm-FAQ.Rd:28-30: Lost braces 28 | {These are the packages I needed in Ubuntu: | ^ checkRd: (-1) ctmm-FAQ.Rd:34: Lost braces 34 | {Make sure that you have the correct \code{timezone} and \code{timeformat} arguments specified. Also, see \code{\link{outlie}}.} | ^ checkRd: (-1) ctmm-FAQ.Rd:38: Lost braces 38 | {\code{R} might not have installed or loaded the package correctly---e.g., some files may have failed to overwrite previous versions---or the workspace/session might be corrupted. Uninstall \code{ctmm}, restart \code{R} without saving the workspace/session, and install \code{ctmm} again.} | ^ checkRd: (-1) ctmm-FAQ.Rd:43-48: Lost braces 43 | {\code{ctmm} has no recursive functions, so I am not exactly sure what causes this error, but it only occurs with certain versions of \code{R} on certain computer architectures. There are several solutions that have worked for people, including restarting \code{R} in a fresh session and updating their software. Alternatively: | ^ checkRd: (-1) ctmm-FAQ.Rd:52: Lost braces 52 | {Namespace collision sometimes occurs between \code{raster}, \code{sp}, \code{move}, and \code{ctmm}. Either restart \code{R} and only load the \code{ctmm} package, or run \code{ctmm::plot} instead of \code{plot}.} | ^ checkRd: (-1) ctmm-FAQ.Rd:56: Lost braces 56 | {The default projection in \code{ctmm} does not preserve the direction of North, but better preserves distances for elongated distributions. See the \code{projection} argument in \code{\link{as.telemetry}} and the example in \code{\link[ctmm]{projection}}. The \code{\link{compass}} function is also useful for pointing north.} | ^ checkRd: (-1) ctmm-FAQ.Rd:60: Lost braces 60 | {Namespace collision can occur between \code{raster} and \code{ctmm}. Either restart \code{R} and only load the \code{ctmm} package, or run \code{ctmm::projection} instead of \code{projection}.} | ^ checkRd: (-1) ctmm-FAQ.Rd:64: Lost braces; missing escapes or markup? 64 | {Maximize the plot window and/or increase your screen resolution.} | ^ checkRd: (-1) ctmm-FAQ.Rd:68: Lost braces; missing escapes or markup? 68 | {Click the gear icon in the upper-left corner of the plot window.} | ^ checkRd: (-1) ctmm-FAQ.Rd:72: Lost braces 72 | {Recent versions of \code{manipulate} and/or RStudio seem to have some issues. Sometimes the gear icon does not render unless you re-run the function 2-5 times.} | ^ checkRd: (-1) ctmm-FAQ.Rd:76: Lost braces 76 | {You probably have an outdated copy of the \code{manipulate} package installed. Update \code{R} to the latest version and then update all of your packages. This seems to happen frequently with the MacOS release of \code{R}.} | ^ checkRd: (-1) sigfig.Rd:20: Lost braces; missing escapes or markup? 20 | \item{est}{Can be either confidence-interval estimates with rows {(lower-limit,point-estimate,upper-limit)} or point estimates (with \code{VAR} or \code{SD} also specified).} | ^ Flavors: r-release-macos-arm64, r-release-macos-x86_64