Last updated on 2024-12-22 13:49:22 CET.
Package | ERROR | WARN | NOTE | OK |
---|---|---|---|---|
cubfits | 4 | 9 | ||
EMCluster | 5 | 8 | ||
MixfMRI | 4 | 9 | ||
MixSim | 13 | |||
pbdMPI | 4 | 2 | 7 | |
pbdSLAP | 4 | 2 | 7 | |
pbdZMQ | 13 | |||
phyclust | 10 | 3 | ||
pmclust | 4 | 9 | ||
QZ | 13 |
Current CRAN status: NOTE: 4, OK: 9
Version: 0.1-4
Check: package dependencies
Result: NOTE
Package which this enhances but not available for checking: ‘pbdMPI’
Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Current CRAN status: ERROR: 5, OK: 8
Version: 0.2-16
Check: examples
Result: ERROR
Running examples in ‘EMCluster-Ex.R’ failed
The error most likely occurred in:
> base::assign(".ptime", proc.time(), pos = "CheckExEnv")
> ### Name: EM Algorithm
> ### Title: EM Algorithm for model-based clustering
> ### Aliases: emcluster shortemcluster simple.init 'emret class' 'emobj
> ### object'
> ### Keywords: programming
>
> ### ** Examples
>
> library(EMCluster, quietly = TRUE)
> set.seed(1234)
> x1 <- da1$da
>
> emobj <- simple.init(x1, nclass = 10)
*** caught segfault ***
address 0x1, cause 'memory not mapped'
Traceback:
1: init.EM(x, nclass = nclass, lab = lab, EMC = EMC, stable.solution = stable.solution, min.n = min.n, min.n.iter = min.n.iter, method = "Rnd.EM")
2: rand.EM(x, nclass, EMC = .emc, stable.solution = FALSE, min.n.iter = 1)
3: simple.init(x1, nclass = 10)
An irrecoverable exception occurred. R is aborting now ...
Segmentation fault
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc
Version: 0.2-16
Check: examples
Result: ERROR
Running examples in ‘EMCluster-Ex.R’ failed
The error most likely occurred in:
> ### Name: EM Algorithm
> ### Title: EM Algorithm for model-based clustering
> ### Aliases: emcluster shortemcluster simple.init 'emret class' 'emobj
> ### object'
> ### Keywords: programming
>
> ### ** Examples
>
> library(EMCluster, quietly = TRUE)
> set.seed(1234)
> x1 <- da1$da
>
> emobj <- simple.init(x1, nclass = 10)
*** caught segfault ***
address 0x1, cause 'memory not mapped'
Traceback:
1: init.EM(x, nclass = nclass, lab = lab, EMC = EMC, stable.solution = stable.solution, min.n = min.n, min.n.iter = min.n.iter, method = "Rnd.EM")
2: rand.EM(x, nclass, EMC = .emc, stable.solution = FALSE, min.n.iter = 1)
3: simple.init(x1, nclass = 10)
An irrecoverable exception occurred. R is aborting now ...
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Version: 0.2-16
Check: examples
Result: ERROR
Running examples in 'EMCluster-Ex.R' failed
The error most likely occurred in:
> ### Name: EM Algorithm
> ### Title: EM Algorithm for model-based clustering
> ### Aliases: emcluster shortemcluster simple.init 'emret class' 'emobj
> ### object'
> ### Keywords: programming
>
> ### ** Examples
>
> library(EMCluster, quietly = TRUE)
> set.seed(1234)
> x1 <- da1$da
>
> emobj <- simple.init(x1, nclass = 10)
Flavor: r-devel-windows-x86_64
Current CRAN status: NOTE: 4, OK: 9
Version: 0.1-4
Check: package dependencies
Result: NOTE
Package which this enhances but not available for checking: ‘pbdMPI’
Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Current CRAN status: OK: 13
Current CRAN status: ERROR: 4, WARN: 2, OK: 7
Version: 0.5-2
Check: whether the namespace can be unloaded cleanly
Result: WARN
---- unloading
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Version: 0.5-2
Check: whether package can be installed
Result: ERROR
Installation failed.
Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Current CRAN status: ERROR: 4, NOTE: 2, OK: 7
Version: 0.3-7
Check: package dependencies
Result: ERROR
Package required but not available: ‘pbdMPI’
See section ‘The DESCRIPTION file’ in the ‘Writing R Extensions’
manual.
Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Version: 0.3-7
Check: installed package size
Result: NOTE
installed size is 5.6Mb
sub-directories of 1Mb or more:
lib 2.9Mb
libs 2.4Mb
Flavors: r-release-windows-x86_64, r-oldrel-windows-x86_64
Current CRAN status: OK: 13
Current CRAN status: NOTE: 10, OK: 3
Version: 0.1-34
Check: Rd files
Result: NOTE
checkRd: (-1) 11_d.init.method.Rd:22-23: Lost braces in \itemize; meant \describe ?
checkRd: (-1) 11_d.init.method.Rd:24-25: Lost braces in \itemize; meant \describe ?
checkRd: (-1) 11_d.init.method.Rd:26-27: Lost braces in \itemize; meant \describe ?
checkRd: (-1) 11_d.init.method.Rd:28-29: Lost braces in \itemize; meant \describe ?
checkRd: (-1) 11_d.init.method.Rd:30-31: Lost braces in \itemize; meant \describe ?
checkRd: (-1) 11_d.init.method.Rd:32: Lost braces in \itemize; meant \describe ?
checkRd: (-1) 11_d.init.procedure.Rd:21-23: Lost braces in \itemize; meant \describe ?
checkRd: (-1) 11_d.init.procedure.Rd:24-26: Lost braces in \itemize; meant \describe ?
checkRd: (-1) 11_d.init.procedure.Rd:27-30: Lost braces in \itemize; meant \describe ?
checkRd: (-1) 11_d.init.procedure.Rd:31-35: Lost braces in \itemize; meant \describe ?
checkRd: (-1) as.star.tree.Rd:26: Lost braces in \itemize; meant \describe ?
checkRd: (-1) as.star.tree.Rd:27: Lost braces in \itemize; meant \describe ?
checkRd: (-1) as.star.tree.Rd:28: Lost braces in \itemize; meant \describe ?
checkRd: (-1) as.star.tree.Rd:29: Lost braces in \itemize; meant \describe ?
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
Current CRAN status: ERROR: 4, OK: 9
Version: 0.2-1
Check: package dependencies
Result: ERROR
Package required but not available: ‘pbdMPI’
See section ‘The DESCRIPTION file’ in the ‘Writing R Extensions’
manual.
Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64
Current CRAN status: OK: 13
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.