* using log directory 'd:/RCompile/CRANincoming/R-devel/FlowerMate.Rcheck' * using R Under development (unstable) (2024-06-13 r86731 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 13.2.0 GNU Fortran (GCC) 13.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'FlowerMate/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'FlowerMate' version '1.0' * package encoding: UTF-8 * checking CRAN incoming feasibility ... NOTE Maintainer: 'A. J. Muñoz-Pajares ' New submission Possibly misspelled words in DESCRIPTION: dimorphic (10:192) enantiostylous (10:241) heterostylous (10:134, 10:278) stylar (10:185) trimorphic (10:206) unidimensional (10:23) * 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 hidden files and directories ... OK * checking for portable file names ... OK * checking serialization versions ... OK * checking whether package 'FlowerMate' can be installed ... OK * checking installed package size ... OK * checking package directory ... OK * checking for future file timestamps ... OK * checking 'build' 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 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 ... OK * checking Rd files ... NOTE checkRd: (-1) FlowerMate-package.Rd:22: Lost braces 22 | Simón-Porcar VI, Muñoz-Pajares AJ, Arroyo J, Johnson SD (2023). Multidimensional reciprocity and inaccuracy indexes in style-polymorphic plant populations. /bold{biorXiv/methods in Ecology and Evolution} | ^ checkRd: (-1) inaccuracy.Rd:27: Lost braces 27 | The input dataframe must contain one row per measured sex organ and at least ¬bold{seven} columns with the following colnames: \bold{pop_code} (population names), \bold{morph} ("L" or "S" to identify long- and short-styled morphs, respectively, for distylous population datasets and "L", "M", "S" to identify long-, mid- and short-styled morphs, respectively, for tristylous plants; this nomenclature should be used also for any other stylar dimorphism or trimorphism analysed; we suggest that in enantiostylous populations, for instance, “L” and “S” are used for left-handed and right-handed morphs, respectively); \bold{ID_indiv} (individual names); \bold{ID_sexorg} (a numeric ID for every sex organ measured in the population), \bold{sexorg} ("ST" for stamen and "AN" for anther. Categories within sex organs can be defined adding a number, such as "ST1", "ST2",...), \bold{x} (position of the sex organ within the x dimension), \bold{y} (position of the sex organ within the y dimension), \bold{z} (position of the sex organ within the x dimension). See data(distylous) to get an example.} | ^ checkRd: (-1) inaccuracy.Rd:79: Lost braces 79 | Simón-Porcar VI, Muñoz-Pajares AJ, Arroyo J, Johnson SD (2023). Multidimensional reciprocity and inaccuracy indexes in style-polymorphic plant populations. /bold{biorXiv/methods in Ecology and Evolution} | ^ * 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 installed files from 'inst/doc' ... OK * checking files in 'vignettes' ... OK * checking examples ... OK * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... [39s] OK * checking PDF version of manual ... [13s] OK * checking HTML version of manual ... OK * DONE Status: 2 NOTEs