* using log directory ‘/data/gannet/ripley/R/packages/tests-devel/GreedyExperimentalDesign.Rcheck’
* using R Under development (unstable) (2025-02-14 r87716)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
    GNU Fortran (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
* running under: Fedora Linux 40 (Workstation Edition)
* using session charset: UTF-8
* using option ‘--no-stop-on-test-error’
* checking for file ‘GreedyExperimentalDesign/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘GreedyExperimentalDesign’ version ‘1.5.6.1’
* package encoding: UTF-8
* 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 whether package ‘GreedyExperimentalDesign’ can be installed ... [45s/51s] OK
See 'https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-gcc/GreedyExperimentalDesign-00install.html' for details.
* used C++ compiler: ‘g++ (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)’
* checking package directory ... 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 ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking whether startup messages can be suppressed ... 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 ... [23s/31s] OK
* checking Rd files ... NOTE
checkRd: (-1) greedy_orthogonalization_curation.Rd:10: Lost braces; missing escapes or markup?
    10 | \item{W}{A matrix in ${-1, 1}^{R x n}$ which have R allocation vectors for an experiment of sample size n.}
       |                       ^
checkRd: (-1) greedy_orthogonalization_curation.Rd:10: Lost braces; missing escapes or markup?
    10 | \item{W}{A matrix in ${-1, 1}^{R x n}$ which have R allocation vectors for an experiment of sample size n.}
       |                               ^
checkRd: (-1) greedy_orthogonalization_curation2.Rd:10: Lost braces; missing escapes or markup?
    10 | \item{W}{A matrix in ${-1, 1}^{R x n}$ which have R allocation vectors for an experiment of sample size n.}
       |                       ^
checkRd: (-1) greedy_orthogonalization_curation2.Rd:10: Lost braces; missing escapes or markup?
    10 | \item{W}{A matrix in ${-1, 1}^{R x n}$ which have R allocation vectors for an experiment of sample size n.}
       |                               ^
checkRd: (-1) initBinaryMatchExperimentalDesignSearch.Rd:36: Lost braces; missing escapes or markup?
    36 | a search through $1_{T}$ space for pairwise match designs based on the structure computed in the function \code{computeBinaryMatchStructure}. 
       |                     ^
checkRd: (-1) initGreedyExperimentalDesignObject.Rd:71: Lost braces; missing escapes or markup?
    71 | a search through $1_{T}$ space for forced balance designs. For debugging, you can use set the \code{seed}
       |                     ^
checkRd: (-1) initGreedyMultipleKernelExperimentalDesignObject.Rd:82: Lost braces; missing escapes or markup?
    82 | a search through $1_{T}$ space for forced balance designs. For debugging, you can use set the \code{seed}
       |                     ^
checkRd: (-1) initKarpExperimentalDesignObject.Rd:31: Lost braces; missing escapes or markup?
    31 | a search through $1_{T}$ space. Note that the Karp search only works 
       |                     ^
checkRd: (-1) initOptimalExperimentalDesignObject.Rd:39: Lost braces; missing escapes or markup?
    39 | a search through $1_{T}$ space. Since this search takes exponential time, for most machines, 
       |                     ^
checkRd: (-1) initRerandomizationExperimentalDesignObject.Rd:53: Lost braces; missing escapes or markup?
    53 | a search through $1_{T}$ space for forced-balance designs. For debugging, you can use set the \code{seed}
       |                     ^
* 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 ... 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 ... OK
* checking PDF version of manual ... [9s/12s] OK
* checking HTML version of manual ... OK
* checking for non-standard things in the check directory ... OK
* checking for detritus in the temp directory ... OK
* DONE
Status: 1 NOTE