• using R Under development (unstable) (2012-08-11 r60235)
  • using platform: x86_64-unknown-linux-gnu (64-bit)
  • using session charset: UTF-8
  • checking for file ‘bear/DESCRIPTION’ ... OK
  • this is package ‘bear’ version ‘2.5.3’
  • 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.
    CRAN requires a NAMESPACE file for all submissions.
  • checking for executable files ... OK
  • checking for hidden files and directories ... OK
  • checking whether package ‘bear’ 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 loading without being on the library search path ... 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
    File ‘bear/R/zzz.R’:
    .First.lib calls:
    cat("\n")
    cat("\n")
    cat("***********************************************************************\n")
    cat(" \n")
    cat(" bear \n")
    cat(" v 2.5.3 \n")
    cat(" http://pkpd.kmu.edu.tw/bear \n")
    cat(" \n")
    cat(" This package is designed to analyze average bioequivalence (ABE) \n")
    cat(" (NCA -> ANOVA) or bioavailability (NCA only) data, with study \n")
    cat(" design of a standard RT/TR 2-treatment, 2-sequence, and 2-period, \n")
    cat(" crossover design (2x2x2), or a replicate ABE study including \n")
    cat(" 2-treatment, 2-sequence, with more than 2 periods (i.e., 2x2x3/ \n")
    cat(" 2x2x4/.../2x2x6), or a parallel ABE study (2x2x1). Bear can be \n")
    cat(" used for SINGLE-DOSE or MULTIPLE-DOSE BE STUDY. \n")
    cat(" \n")
    cat(" Please type 'go()' to get started. \n")
    cat(" \n")
    cat("***********************************************************************\n")

    Package startup functions should use ‘packageStartupMessage’ to
    generate messages.
    See section ‘Good practice’ in ?.onAttach.
  • checking Rd files ... OK
  • 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 contents of ‘data’ directory ... OK
  • checking data for non-ASCII characters ... OK
  • checking data for ASCII and uncompressed saves ... OK
  • checking examples ... NONE
  • checking PDF version of manual ... OK
    NOTE: There were 2 notes.
    See
    ‘/home/hornik/tmp/R.check/r-devel/Work/PKGS/bear.Rcheck/00check.log’
    for details.