CRAN Package Check Results for Package ADPclust

Last updated on 2024-11-21 19:52:30 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.7 2.82 47.06 49.88 NOTE
r-devel-linux-x86_64-debian-gcc 0.7 1.99 35.21 37.20 NOTE
r-devel-linux-x86_64-fedora-clang 0.7 86.81 NOTE
r-devel-linux-x86_64-fedora-gcc 0.7 96.09 NOTE
r-devel-windows-x86_64 0.7 4.00 70.00 74.00 NOTE
r-patched-linux-x86_64 0.7 2.76 45.75 48.51 NOTE
r-release-linux-x86_64 0.7 2.58 46.29 48.87 NOTE
r-release-macos-arm64 0.7 34.00 NOTE
r-release-macos-x86_64 0.7 52.00 NOTE
r-release-windows-x86_64 0.7 4.00 90.00 94.00 NOTE
r-oldrel-macos-arm64 0.7 39.00 OK
r-oldrel-macos-x86_64 0.7 53.00 OK
r-oldrel-windows-x86_64 0.7 5.00 89.00 94.00 OK

Check Details

Version: 0.7
Check: Rd files
Result: NOTE checkRd: (-1) FindCentersAutoV.Rd:27: Lost braces; missing escapes or markup? 27 | Given f's and delta's, cluster centers are chosen to be the data points whose delta values are high and f values are larger than a fixed threshold. To be more specific, let F denote the set of all f(x). centers are selected as points with the largest m delta values in the set {x | f(x) > a'th percentile of F}. The number of centers m is given by the parameter nclust. The cutting percentile a is given by the parameter f.cut. When at least one of these two parameters are vectors, centers are selected based all combinations of them, and returned in a list. | ^ checkRd: (-1) FindClustersAuto.Rd:26: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) FindClustersAuto.Rd:27: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) FindClustersAuto.Rd:28: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) FindClustersAuto.Rd:29: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) FindClustersManual.Rd:19: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) FindClustersManual.Rd:20: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) FindClustersManual.Rd:21: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) FindClustersManual.Rd:22: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) FindFD.Rd:16: Lost braces in \itemize; meant \describe ? checkRd: (-1) FindFD.Rd:17: Lost braces in \itemize; meant \describe ? checkRd: (-1) FindFD.Rd:18: Lost braces in \itemize; meant \describe ? checkRd: (-1) adpclust.Rd:28: Lost braces in \itemize; meant \describe ? checkRd: (-1) adpclust.Rd:29: Lost braces in \itemize; meant \describe ? checkRd: (-1) adpclust.Rd:36: Lost braces in \itemize; meant \describe ? checkRd: (-1) adpclust.Rd:37: Lost braces in \itemize; meant \describe ? checkRd: (-1) adpclust.Rd:38: Lost braces in \itemize; meant \describe ? checkRd: (-1) adpclust.Rd:48: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) adpclust.Rd:49: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) adpclust.Rd:50: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) adpclust.Rd:51: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) adpclust.Rd:52: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) adpclust.Rd:53: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) adpclust.Rd:54: Lost braces in \itemize; \value handles \item{}{} directly checkRd: (-1) adpclust.Rd:55: 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

Version: 0.7
Check: dependencies in R code
Result: NOTE Namespaces in Imports field not imported from: ‘fields’ ‘knitr’ All declared Imports should be used. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

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.