CRAN Package Check Results for Package PointFore

Last updated on 2025-06-23 02:50:26 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.2.0 5.41 117.65 123.06 NOTE
r-devel-linux-x86_64-debian-gcc 0.2.0 3.96 78.69 82.65 NOTE
r-devel-linux-x86_64-fedora-clang 0.2.0 191.80 NOTE
r-devel-linux-x86_64-fedora-gcc 0.2.0 210.88 NOTE
r-devel-windows-x86_64 0.2.0 8.00 0.00 8.00 FAIL
r-patched-linux-x86_64 0.2.0 5.19 109.29 114.48 NOTE
r-release-linux-x86_64 0.2.0 5.01 111.35 116.36 NOTE
r-release-macos-arm64 0.2.0 58.00 NOTE
r-release-macos-x86_64 0.2.0 102.00 NOTE
r-release-windows-x86_64 0.2.0 7.00 117.00 124.00 NOTE
r-oldrel-macos-arm64 0.2.0 55.00 NOTE
r-oldrel-macos-x86_64 0.2.0 81.00 NOTE
r-oldrel-windows-x86_64 0.2.0 9.00 155.00 164.00 NOTE

Check Details

Version: 0.2.0
Check: CRAN incoming feasibility
Result: NOTE Maintainer: ‘Patrick Schmidt <pschmidte@gmail.com>’ The Description field contains Katzfuss and Gneiting (2015) <arXiv:1506.01917> for more details on the Please refer to arXiv e-prints via their arXiv DOI <doi:10.48550/arXiv.YYMM.NNNNN>. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc

Version: 0.2.0
Check: Rd files
Result: NOTE checkRd: (-1) estimate.functional.Rd:34: Lost braces; missing escapes or markup? 34 | \item{bw}{function describing bandwidth selection (see ?gmm for alternatives). Standard is that the bandwidth depends on the sample length $T$ by $m(T)=T^{1/5}$.} | ^ 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.2.0
Check: dependencies in R code
Result: NOTE Namespaces in Imports field not imported from: ‘car’ ‘lubridate’ All declared Imports should be used. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 0.2.0
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: $coefficients Estimate Std. Error t value Pr(>|t|) Theta[1] 0.5681818 0.0470286 12.08162 1.320854e-33 $Jtest ## J-Test: degrees of freedom is 0 ## J-test P-value Test E(g)=0: 3.0278834512059e-15 ******* > > > > ### * <FOOTER> > ### > cleanEx() > options(digits = 7L) > base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n") Time elapsed: 6.45 0.21 6.67 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