Last updated on 2024-11-24 15:49:57 CET.
Package | NOTE | OK |
---|---|---|
metRology | 10 | 3 |
Current CRAN status: NOTE: 10, OK: 3
Version: 0.9-28-1
Check: Rd files
Result: NOTE
checkRd: (-1) bootMSD.Rd:71: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD.Rd:72: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD.Rd:73: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD.Rd:74-75: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD.Rd:76-77: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD.Rd:78: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD.Rd:79: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD.Rd:80-81: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD_class.Rd:103: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD_class.Rd:104: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD_class.Rd:105: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD_class.Rd:106-107: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD_class.Rd:108-109: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD_class.Rd:110: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD_class.Rd:111-112: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD_class.Rd:113: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) bootMSD_class.Rd:114: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) plot.uncert.Rd:47: Lost braces
47 | absolute value is plotted. For the 'diagonal' terms, these are just eqn{u_i(y)}
| ^
checkRd: (-1) plot.uncertMC.Rd:52: Lost braces
52 | present (in sQuote{\dots}), it is set to \code{TRUE}.}
| ^
checkRd: (-1) plot.uncertMC.Rd:56: Lost braces
56 | \item{\code{which=4}}{A bar plot of eqn{cor(x_i,y)} if \code{x$y}
| ^
checkRd: (-1) plot.uncertMC.Rd:59: Lost braces
59 | \item{\code{which=5}}{A bar plot of eqn{cov(x_i,y)} if \code{x$y}
| ^
checkRd: (-1) xs.plot.Rd:146: Lost braces
146 | Options are code{"top"}, code{"topright"}, code{"right"}, code{"bottomright"},
| ^
checkRd: (-1) xs.plot.Rd:146: Lost braces
146 | Options are code{"top"}, code{"topright"}, code{"right"}, code{"bottomright"},
| ^
checkRd: (-1) xs.plot.Rd:146: Lost braces
146 | Options are code{"top"}, code{"topright"}, code{"right"}, code{"bottomright"},
| ^
checkRd: (-1) xs.plot.Rd:146: Lost braces
146 | Options are code{"top"}, code{"topright"}, code{"right"}, code{"bottomright"},
| ^
checkRd: (-1) xs.plot.Rd:147: Lost braces
147 | code{"bottom"}, code{"bottomleft"}, code{"left"} and code{"topleft"}. A vector can be
| ^
checkRd: (-1) xs.plot.Rd:147: Lost braces
147 | code{"bottom"}, code{"bottomleft"}, code{"left"} and code{"topleft"}. A vector can be
| ^
checkRd: (-1) xs.plot.Rd:147: Lost braces
147 | code{"bottom"}, code{"bottomleft"}, code{"left"} and code{"topleft"}. A vector can be
| ^
checkRd: (-1) xs.plot.Rd:147: Lost braces
147 | code{"bottom"}, code{"bottomleft"}, code{"left"} and code{"topleft"}. A vector can be
| ^
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.9-28-1
Check: Rd cross-references
Result: NOTE
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
GUM.Rd: grad
cov.dellipse.Rd: scaleTau2, s_Qn, s_mad, s_IQR, covMcd, cov.mcd,
covOGK, covGK, cov.mve, cov.rob
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-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.