Last updated on 2025-07-28 13:49:26 CEST.
| Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
|---|---|---|---|---|---|---|
| r-devel-linux-x86_64-debian-clang | 1.20 | 14.33 | 126.63 | 140.96 | OK | |
| r-devel-linux-x86_64-debian-gcc | 1.20 | 10.88 | 89.02 | 99.90 | OK | |
| r-devel-linux-x86_64-fedora-clang | 1.20 | 216.17 | OK | |||
| r-devel-linux-x86_64-fedora-gcc | 1.20 | 237.66 | OK | |||
| r-devel-windows-x86_64 | 1.20 | 26.00 | 178.00 | 204.00 | OK | |
| r-patched-linux-x86_64 | 1.19 | 13.65 | 117.78 | 131.43 | NOTE | |
| r-release-linux-x86_64 | 1.20 | 14.10 | 114.84 | 128.94 | OK | |
| r-release-macos-arm64 | 1.20 | 78.00 | OK | |||
| r-release-macos-x86_64 | 1.20 | 130.00 | OK | |||
| r-release-windows-x86_64 | 1.20 | 18.00 | 162.00 | 180.00 | OK | |
| r-oldrel-macos-arm64 | 1.20 | 76.00 | OK | |||
| r-oldrel-macos-x86_64 | 1.20 | 127.00 | OK | |||
| r-oldrel-windows-x86_64 | 1.20 | 24.00 | 192.00 | 216.00 | OK |
Version: 1.19
Check: Rd files
Result: NOTE
checkRd: (-1) Anthropometry-internalHipamAnthropom.Rd:16: Lost braces; missing escapes or markup?
16 | Several internal functions used by both $HIPAM_{MO}$ and $HIPAM_{IMO}$ algorithms
| ^
checkRd: (-1) Anthropometry-internalHipamAnthropom.Rd:16: Lost braces; missing escapes or markup?
16 | Several internal functions used by both $HIPAM_{MO}$ and $HIPAM_{IMO}$ algorithms
| ^
checkRd: (-1) Anthropometry-internalHipamAnthropom.Rd:19: Lost braces; missing escapes or markup?
19 | This file contains several functions called for both $HIPAM_{MO}$ and $HIPAM_{IMO}$ algorithms. Therefore, they are not used directly.
| ^
checkRd: (-1) Anthropometry-internalHipamAnthropom.Rd:19: Lost braces; missing escapes or markup?
19 | This file contains several functions called for both $HIPAM_{MO}$ and $HIPAM_{IMO}$ algorithms. Therefore, they are not used directly.
| ^
checkRd: (-1) Anthropometry-internalHipamAnthropom.Rd:21: Lost braces; missing escapes or markup?
21 | The $HIPAM_{MO}$ and $HIPAM_{IMO}$ algorithms are different in the way to generate and validate a clustering partition. However, the functions related to the further clustering steps are common to both of them. These functions are those collected in this file.
| ^
checkRd: (-1) Anthropometry-internalHipamAnthropom.Rd:21: Lost braces; missing escapes or markup?
21 | The $HIPAM_{MO}$ and $HIPAM_{IMO}$ algorithms are different in the way to generate and validate a clustering partition. However, the functions related to the further clustering steps are common to both of them. These functions are those collected in this file.
| ^
checkRd: (-1) Anthropometry-package.Rd:22: Lost braces; missing escapes or markup?
22 | Anthropometry-internalHipamAnthropom: Several internal functions used by both $HIPAM_{MO}$ and $HIPAM_{IMO}$ algorithms.\cr
| ^
checkRd: (-1) Anthropometry-package.Rd:22: Lost braces; missing escapes or markup?
22 | Anthropometry-internalHipamAnthropom: Several internal functions used by both $HIPAM_{MO}$ and $HIPAM_{IMO}$ algorithms.\cr
| ^
checkRd: (-1) Anthropometry-package.Rd:31: Lost braces; missing escapes or markup?
31 | checkBranchLocalIMO: Evaluation of the candidate clustering partition in $HIPAM_{IMO}$.\cr
| ^
checkRd: (-1) Anthropometry-package.Rd:32: Lost braces; missing escapes or markup?
32 | checkBranchLocalMO: Evaluation of the candidate clustering partition in $HIPAM_{MO}$.\cr
| ^
checkRd: (-1) Anthropometry-package.Rd:39: Lost braces; missing escapes or markup?
39 | getBestPamsamIMO: Generation of the candidate clustering partition in $HIPAM_{IMO}$. \cr
| ^
checkRd: (-1) Anthropometry-package.Rd:40: Lost braces; missing escapes or markup?
40 | getBestPamsamMO: Generation of the candidate clustering partition in $HIPAM_{MO}$.\cr
| ^
checkRd: (-1) checkBranchLocalIMO.Rd:4: Lost braces; missing escapes or markup?
4 | Evaluation of the candidate clustering partition in $HIPAM_{IMO}$
| ^
checkRd: (-1) checkBranchLocalIMO.Rd:9: Lost braces; missing escapes or markup?
9 | In this version of HIPAM, called $HIPAM_{IMO}$, there are three different stopping criteria: First, if $|P| leq 2$, then P is a terminal node. If not, the second stopping refers to the INCA (Index Number Clusters Atypical) criterion (Irigoien et al. (2008)): if $INCA_k leq 0.2$ for all k, then P is a terminal node. Finally, the third stopping criteria uses the Mean Split Silhouette. See Vinue et al. (2014) for more details.
| ^
checkRd: (-1) checkBranchLocalIMO.Rd:40: Lost braces; missing escapes or markup?
40 | Option 'IMO' for using $HIPAM_{IMO}$.
| ^
checkRd: (-1) checkBranchLocalIMO.Rd:70: Lost braces; missing escapes or markup?
70 | This function belongs to the $HIPAM_{IMO}$ algorithm and it is not solely used. That is why there is no section of \emph{examples} in this help page. See \code{\link{hipamAnthropom}}.
| ^
checkRd: (-1) checkBranchLocalMO.Rd:4: Lost braces; missing escapes or markup?
4 | Evaluation of the candidate clustering partition in $HIPAM_{MO}$
| ^
checkRd: (-1) checkBranchLocalMO.Rd:9: Lost braces; missing escapes or markup?
9 | In this version of HIPAM, called $HIPAM_{MO}$, there are two different stopping criteria: First, if $|P| leq 2$, then P is a terminal node. If not, the second stopping criteria uses the Mean Split Silhouette. See Vinue et al. (2014) for more details.
| ^
checkRd: (-1) checkBranchLocalMO.Rd:40: Lost braces; missing escapes or markup?
40 | Option 'MO' for using $HIPAM_{MO}$.
| ^
checkRd: (-1) checkBranchLocalMO.Rd:66: Lost braces; missing escapes or markup?
66 | This function belongs to the $HIPAM_{MO}$ algorithm and it is not solely used. That is why there is no section of \emph{examples} in this help page. See \code{\link{hipamAnthropom}}.
| ^
checkRd: (-1) getBestPamsamIMO.Rd:4: Lost braces; missing escapes or markup?
4 | Generation of the candidate clustering partition in $HIPAM_{IMO}$
| ^
checkRd: (-1) getBestPamsamIMO.Rd:9: Lost braces; missing escapes or markup?
9 | In this version of HIPAM, called $HIPAM_{IMO}$, the number k of (child) clusters is obtained by using the INCA (Index Number Clusters Atypical) criterion (Irigoien et al. (2008)) in the following way: at each node P, if there is k such that $INCA_k > 0.2$, then the k prior to the first largest slope decrease is selected. However, this procedure does not apply either to the top node or to the generation of the new partitions from which the Mean Split Silhouette is calculated. In these cases, even when all $INCA_k < 0.2$, k = 3 is fixed as the number of groups to divide and proceed. See Vinue et al. (2014) for more details.
| ^
checkRd: (-1) getBestPamsamIMO.Rd:27: Lost braces; missing escapes or markup?
27 | Option 'IMO' for using $HIPAM_{IMO}$.
| ^
checkRd: (-1) getBestPamsamIMO.Rd:74: Lost braces; missing escapes or markup?
74 | This function belongs to the $HIPAM_{IMO}$ algorithm and it is not solely used. That is why there is no section of \emph{examples} in this help page. See \code{\link{hipamAnthropom}}.
| ^
checkRd: (-1) getBestPamsamMO.Rd:4: Lost braces; missing escapes or markup?
4 | Generation of the candidate clustering partition in $HIPAM_{MO}$
| ^
checkRd: (-1) getBestPamsamMO.Rd:9: Lost braces; missing escapes or markup?
9 | In this version of HIPAM, called $HIPAM_{MO}$, the number k of (child) clusters is obtained by maximizing the silhouette width (asw). See Vinue et al. (2014) for more details.
| ^
checkRd: (-1) getBestPamsamMO.Rd:27: Lost braces; missing escapes or markup?
27 | Option 'MO' for using $HIPAM_{MO}$.
| ^
checkRd: (-1) getBestPamsamMO.Rd:70: Lost braces; missing escapes or markup?
70 | This function belongs to the $HIPAM_{MO}$ algorithm and it is not solely used. That is why there is no section of \emph{examples} in this help page. See \code{\link{hipamAnthropom}}.
| ^
checkRd: (-1) hipamAnthropom.Rd:9: Lost braces; missing escapes or markup?
9 | This function is a HIPAM algorithm adapted to deal with anthropometric data. To that end, a different dissimilarity function is incorporated. This function is that explained in McCulloch et al. (1998) and it is implemented in \code{\link{getDistMatrix}}. We call it $d_{MO}$. In addition, a different method to obtain a classification tree is also incorporated.
| ^
checkRd: (-1) hipamAnthropom.Rd:11: Lost braces; missing escapes or markup?
11 | Two HIPAM algorithms are proposed. The first one, called $HIPAM_{MO}$, is a HIPAM that uses $d_{MO}$. The second one, $HIPAM_{IMO}$, is a HIPAM algorithm that uses $d_{MO}$ and the INCA (Index Number Clusters Atypical) statistic criterion (Irigoien et al. (2008)) to decide the number of child clusters and as a stopping rule.
| ^
checkRd: (-1) hipamAnthropom.Rd:11: Lost braces; missing escapes or markup?
11 | Two HIPAM algorithms are proposed. The first one, called $HIPAM_{MO}$, is a HIPAM that uses $d_{MO}$. The second one, $HIPAM_{IMO}$, is a HIPAM algorithm that uses $d_{MO}$ and the INCA (Index Number Clusters Atypical) statistic criterion (Irigoien et al. (2008)) to decide the number of child clusters and as a stopping rule.
| ^
checkRd: (-1) hipamAnthropom.Rd:11: Lost braces; missing escapes or markup?
11 | Two HIPAM algorithms are proposed. The first one, called $HIPAM_{MO}$, is a HIPAM that uses $d_{MO}$. The second one, $HIPAM_{IMO}$, is a HIPAM algorithm that uses $d_{MO}$ and the INCA (Index Number Clusters Atypical) statistic criterion (Irigoien et al. (2008)) to decide the number of child clusters and as a stopping rule.
| ^
checkRd: (-1) hipamAnthropom.Rd:11: Lost braces; missing escapes or markup?
11 | Two HIPAM algorithms are proposed. The first one, called $HIPAM_{MO}$, is a HIPAM that uses $d_{MO}$. The second one, $HIPAM_{IMO}$, is a HIPAM algorithm that uses $d_{MO}$ and the INCA (Index Number Clusters Atypical) statistic criterion (Irigoien et al. (2008)) to decide the number of child clusters and as a stopping rule.
| ^
checkRd: (-1) hipamAnthropom.Rd:36: Lost braces; missing escapes or markup?
36 | Type of HIPAM algorithm to be used. The possible options are 'MO' (for $HIPAM_{MO}$) and 'IMO' (for $HIPAM_{IMO}$).
| ^
checkRd: (-1) hipamAnthropom.Rd:36: Lost braces; missing escapes or markup?
36 | Type of HIPAM algorithm to be used. The possible options are 'MO' (for $HIPAM_{MO}$) and 'IMO' (for $HIPAM_{IMO}$).
| ^
checkRd: (-1) hipamAnthropom.Rd:49: Lost braces; missing escapes or markup?
49 | The $HIPAM_{MO}$ algorithm uses the \code{\link{getBestPamsamMO}} and \code{\link{checkBranchLocalMO}} functions, while the $HIPAM_{IMO}$ algorithm uses the \code{\link{getBestPamsamIMO}} and \code{\link{checkBranchLocalIMO}} functions.
| ^
checkRd: (-1) hipamAnthropom.Rd:49: Lost braces; missing escapes or markup?
49 | The $HIPAM_{MO}$ algorithm uses the \code{\link{getBestPamsamMO}} and \code{\link{checkBranchLocalMO}} functions, while the $HIPAM_{IMO}$ algorithm uses the \code{\link{getBestPamsamIMO}} and \code{\link{checkBranchLocalIMO}} functions.
| ^
checkRd: (-1) hipamAnthropom.Rd:94: Lost braces; missing escapes or markup?
94 | All the functions related to the HIPAM algorithm were originally created by E. Wit et al., and they are available freely on \url{https://www.math.rug.nl/~ernst/book/smida.html}. In order to develop the $HIPAM_{MO}$ and $HIPAM_{IMO}$ algorithms, we have used and adapted them.
| ^
checkRd: (-1) hipamAnthropom.Rd:94: Lost braces; missing escapes or markup?
94 | All the functions related to the HIPAM algorithm were originally created by E. Wit et al., and they are available freely on \url{https://www.math.rug.nl/~ernst/book/smida.html}. In order to develop the $HIPAM_{MO}$ and $HIPAM_{IMO}$ algorithms, we have used and adapted them.
| ^
Flavor: r-patched-linux-x86_64
Version: 1.19
Check: Rd cross-references
Result: NOTE
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
HartiganShapes.Rd: procGPA
LloydShapes.Rd: procGPA
archetypesBoundary.Rd: stepArchetypes, archetypes
archetypoids.Rd: archetypes, stepArchetypes
shapes3dShapes.Rd: shapes3d
stepArchetypesRawData.Rd: stepArchetypes, archetypes
stepArchetypoids.Rd: stepArchetypes, archetypes
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
Flavor: r-patched-linux-x86_64