• using R version 2.14.1 Patched (2012-02-05 r58287)
  • using platform: i686-pc-linux-gnu (32-bit)
  • using session charset: UTF-8
  • checking for file ‘binMto/DESCRIPTION’ ... OK
  • checking extension type ... Package
  • this is package ‘binMto’ version ‘0.0-4’
  • checking package dependencies ... OK
  • checking if this is a source package ... OK
  • checking if there is a namespace ... NOTE
    As from R 2.14.0 all packages need a namespace.
    One will be generated on installation, but it is better to handcraft a
    NAMESPACE file: R CMD build will produce a suitable starting point.
  • checking for executable files ... OK
  • checking whether package ‘binMto’ can be installed ... OK
  • checking installed package size ... OK
  • checking package directory ... OK
  • checking for portable file names ... OK
  • checking for sufficient/correct file permissions ... OK
  • checking DESCRIPTION meta-information ... OK
  • checking top-level files ... OK
  • checking index information ... OK
  • checking package subdirectories ... OK
  • checking R 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 for unstated 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 ... NOTE
    simPowerI: warning in rbinom(n = k + 1, size = n, p = pH1): partial
    argument match of 'p' to 'prob'
  • checking Rd files ... NOTE
    prepare_Rd: Mtoquant.Rd:25-27: Dropping empty section \details
    prepare_Rd: Mtoquant.Rd:40-42: Dropping empty section \examples
    prepare_Rd: binMtoMethods.Rd:29-30: Dropping empty section \details
    prepare_Rd: simPower.Rd:41: Dropping empty section \references
  • checking Rd metadata ... 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 examples ... OK
  • checking PDF version of manual ... OK