Last updated on 2025-07-25 07:50:01 CEST.
| Package | FAIL | NOTE |
|---|---|---|
| marcher | 1 | 12 |
Current CRAN status: FAIL: 1, NOTE: 12
Version: 0.0-2
Check: CRAN incoming feasibility
Result: NOTE
Maintainer: ‘Eliezer Gurarie <egurarie@umd.edu>’
Found the following (possibly) invalid file URI:
URI: Eurodeer.org
From: man/Michela.Rd
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc
Version: 0.0-2
Check: Rd files
Result: NOTE
checkRd: (-1) locate_shift.Rd:29: Lost braces
29 | \code{\link{quickfit}}, code{\link{locator}}
| ^
checkRd: (-1) marcher-package.Rd:14: Lost braces; missing escapes or markup?
14 | 1. \code{\link{estimate_shift}} {Estimate a range shift process.}
| ^
checkRd: (-1) marcher-package.Rd:16: Lost braces; missing escapes or markup?
16 | 2. \code{\link{simulate_shift}} {Simulate a range shift process.}
| ^
checkRd: (-1) marcher-package.Rd:18: Lost braces; missing escapes or markup?
18 | 3. \code{\link{plot.shiftfit}} {Visualize a range shift process.}
| ^
checkRd: (-1) marcher-package.Rd:20: Lost braces; missing escapes or markup?
20 | 4. \code{\link{test_rangeshift}} {Test whether a range shift occurred.}
| ^
checkRd: (-1) marcher-package.Rd:22: Lost braces; missing escapes or markup?
22 | 5. \code{\link{test_return}} {Test whether a migration was a return migration.}
| ^
checkRd: (-1) marcher-package.Rd:24: Lost braces; missing escapes or markup?
24 | 6. \code{\link{test_stopover}} {Test whether a stopover occurred during a migration.}
| ^
checkRd: (-1) quickfit.Rd:25: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) quickfit.Rd:26: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) test_rangeshift.Rd:25: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) test_rangeshift.Rd:26: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) test_rangeshift.Rd:27: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) test_rangeshift.Rd:28: 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
Version: 0.0-2
Check: PDF version of manual
Result: FAIL
Check process probably crashed or hung up for 20 minutes ... killed
Most likely this happened in the example checks (?),
if not, ignore the following last lines of example output:
> # mean parameters (t1,dt)
> mus <- c(t1=t1,dt=dt,x1=x1,y1=y1,x2=x2,y2=y2)
> # time-scale parameters
> taus <- c(tau.z = tau.z, tau.v = tau.v)
>
> # generate and plot mean vector
> T <- 1:200
> Mu <- getMu(T, mus)
>
> # simulate and plot MOUF process
> SimTrack <- simulate_shift(T, tau=taus, Mu, A=A)
> with(SimTrack, scan_track(time=T,x=X,y=Y))
>
>
>
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed: 8.6 1.05 9.66 NA NA
> grDevices::dev.off()
null device
1
> ###
> ### Local variables: ***
> ### mode: outline-minor ***
> ### outline-regexp: "\\(> \\)?### [*]+" ***
> ### End: ***
> quit('no')
======== End of example output (where/before crash/hang up occured ?) ========
Flavor: r-devel-windows-x86_64