Last updated on 2025-05-31 13:50:11 CEST.
| Package | FAIL | OK |
|---|---|---|
| mousetRajectory | 13 | |
| pplot | 13 | |
| schoRsch | 1 | 12 |
Current CRAN status: OK: 13
Current CRAN status: OK: 13
Current CRAN status: FAIL: 1, OK: 12
Version: 1.11
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:
+ cond1,cond2)
> zscores(data,dv="measurements",
+ factors=c("cond1","cond2"))
[1] -0.7071068 0.7071068 0.7071068 -0.7071068 -0.7071068 0.7071068 -0.7071068
[8] 0.7071068
>
> # Operating on column indices
> zscores(data,dv=1,
+ factors=3)
[1] -0.7169282 0.2048366 0.4629100 0.0000000 -0.8193465 1.3314380 -1.3887301
[8] 0.9258201
>
>
>
>
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed: 0.36 0.05 0.4 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-release-windows-x86_64