Last updated on 2024-11-21 19:53:16 CET.
Package | ERROR | NOTE | OK |
---|---|---|---|
clustur | 3 | 4 | 5 |
mpactr | 13 | ||
phylotypr | 6 | 7 |
Current CRAN status: ERROR: 3, NOTE: 4, OK: 5
Version: 0.1.0
Check: examples
Result: ERROR
Running examples in ‘clustur-Ex.R’ failed
The error most likely occurred in:
> base::assign(".ptime", proc.time(), pos = "CheckExEnv")
> ### Name: cluster
> ### Title: Cluster entities together
> ### Aliases: cluster
>
> ### ** Examples
>
>
> cutoff <- 0.03
> count_table <- read_count(example_path("amazon.full.count_table"))
> distance_data <- read_dist(example_path("amazon_column.dist"),
+ count_table, cutoff)
Please enter a valid file path
Error: Invalid file path.
Execution halted
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-patched-linux-x86_64
Version: 0.1.0
Check: re-building of vignette outputs
Result: ERROR
Error(s) in re-building vignettes:
...
--- re-building ‘clustur.Rmd’ using rmarkdown
Quitting from lines 76-77 [unnamed-chunk-3] (clustur.Rmd)
Error: processing vignette 'clustur.Rmd' failed with diagnostics:
Invalid file path.
--- failed re-building ‘clustur.Rmd’
SUMMARY: processing the following file failed:
‘clustur.Rmd’
Error: Vignette re-building failed.
Execution halted
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-patched-linux-x86_64
Version: 0.1.0
Check: installed package size
Result: NOTE
installed size is 18.8Mb
sub-directories of 1Mb or more:
libs 18.4Mb
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: NOTE: 6, OK: 7
Version: 0.1.0
Check: installed package size
Result: NOTE
installed size is 5.3Mb
sub-directories of 1Mb or more:
data 1.6Mb
doc 2.1Mb
Flavors: 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
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.