* using log directory ‘/home/hornik/tmp/R.check/r-devel-clang/Work/PKGS/wavethresh.Rcheck’ * using R Under development (unstable) (2024-04-27 r86487) * using platform: x86_64-pc-linux-gnu * R was compiled by Debian clang version 18.1.4 (1) Debian flang-new version 18.1.4 (1) * running under: Debian GNU/Linux trixie/sid * using session charset: UTF-8 * checking for file ‘wavethresh/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘wavethresh’ version ‘4.7.2’ * checking package namespace information ... OK * checking package dependencies ... OK * checking if this is a source package ... OK * checking if there is a namespace ... OK * checking for executable files ... OK * checking for hidden files and directories ... OK * checking for portable file names ... OK * checking for sufficient/correct file permissions ... OK * checking serialization versions ... OK * checking whether package ‘wavethresh’ can be installed ... OK See 'https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/wavethresh-00install.html' for details. * used C compiler: ‘Debian clang version 18.1.4 (1)’ * checking package directory ... OK * checking for future file timestamps ... OK * checking DESCRIPTION meta-information ... OK * checking top-level files ... OK * checking for left-over files ... OK * checking index information ... OK * checking package subdirectories ... OK * checking code files for non-ASCII characters ... OK * checking R files for syntax errors ... OK * checking whether the package can be loaded ... [0s/0s] OK * checking whether the package can be loaded with stated dependencies ... [0s/1s] OK * checking whether the package can be unloaded cleanly ... [0s/0s] OK * checking whether the namespace can be loaded with stated dependencies ... [0s/1s] OK * checking whether the namespace can be unloaded cleanly ... [0s/0s] OK * checking loading without being on the library search path ... [0s/0s] OK * checking whether startup messages can be suppressed ... [0s/1s] OK * checking use of S3 registration ... OK * checking dependencies in R code ... OK * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... [59s/67s] OK * checking Rd files ... [4s/5s] NOTE checkRd: (-1) accessC.wst.rd:24: Lost braces 24 | Note that coefficients returned by this function are in emph{packet order}. They can be used \emph{as is} but for many applications it might be more useful to deal with the coefficients in packets: see the function \code{\link{getpacket.wst}} for further details. | ^ checkRd: (-1) griddata.rd:18: Lost braces 18 | \code{G}{Codes the value of the linear interpolant matrix for the corresponding entry in \code{gridt}. The value at each point corresponds to the proportion of the original data point pointed to by \code{Gindex} that contributes to the new value at the corresponding \code{gridt} value. See Kovac, (1997), page 81 for further information.} | ^ checkRd: (-1) makegrid.rd:13: Lost braces; missing escapes or markup? 13 | \item{gridn}{The number of grid points in the dyadic grid that the (x,y) gets interpolated to. By default this is the next power of two larger than the length of {x}.} | ^ checkRd: (-1) makewpstDO.rd:29: Lost braces 29 | /bold{12}, 45-56. | ^ checkRd: (-1) wd.object.rd:47: Lost braces 47 | The wd class of objects has methods for the following generic functions: \code{\link{plot}}, \code{\link{threshold}}, \code{\link{summary}}, \code{\link{print}}, code{\link{draw}}. | ^ * checking Rd metadata ... OK * checking Rd line widths ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking contents of ‘data’ directory ... OK * checking data for non-ASCII characters ... [0s/1s] OK * checking data for ASCII and uncompressed saves ... OK * checking line endings in C/C++/Fortran sources/headers ... OK * checking pragmas in C/C++ headers and code ... OK * checking compilation flags used ... OK * checking compiled code ... OK * checking examples ... [6s/7s] OK * checking PDF version of manual ... [24s/29s] OK * checking HTML version of manual ... [17s/26s] OK * checking for non-standard things in the check directory ... OK * DONE Status: 1 NOTE