Last updated on 2024-12-22 13:49:21 CET.
Package | NOTE | OK |
---|---|---|
lfstat | 10 | 3 |
Current CRAN status: NOTE: 10, OK: 3
Version: 0.9.12
Check: Rd files
Result: NOTE
checkRd: (-1) flowunit.Rd:30: Lost braces; missing escapes or markup?
30 | Usually flow units are of dimension $L^3 T^{-1}$. Currently a length $l$ can be on of \code{c("metre", "cm", "centimetre" "litre")}, whereas time $T$ can be one in \code{c("days", "hours", "mins", "secs")}, possibly abbreviated. The numerator of the fraction (everything before the literal \code{"/"}) is interpreted as the length (superscripts like \code{"^3"} are discarded), the denominator as time. E.g. valid units would be \code{"cm^3/s"}, \code{"m^3/day"} or \code{"litre/sec"}.
| ^
checkRd: (-1) seasindex.Rd:30: Lost braces
30 | Laaha, G. and Bl{\"o}schl, G. (2006), Seasonality indices for regionalizing
| ^
checkRd: (-1) seasindex.Rd:34: Lost braces
34 | Mitteilungen, Inst. f{\"u}r Wasserbau u. Ingenieurhydrologie,
| ^
checkRd: (-1) seasratio.Rd:31: Lost braces
31 | Laaha, G. and Bl{\"o}schl, G. (2006), Seasonality indices for regionalizing low flows. Hydrol. Process., 20
| ^
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.12
Check: Rd cross-references
Result: NOTE
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
apply.seasonal.Rd: apply.daily, apply.monthly, apply.yearly
as.xts.lfobj.Rd: as.xts
cdf_ev.Rd: lmom
fill_na.Rd: na.approx
plot.deficit.Rd: plot.xts, dygraph
rfa.Rd: regfit, lmom-package
rfaplot.Rd: lmrd, lmom-package
sbplot.Rd: barchart
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.