* using log directory 'd:/Rcompile/CRANpkg/local/2.15/moduleColor.Rcheck'
* using R version 2.15.0 (2012-03-30)
* using platform: x86_64-pc-mingw32 (64-bit)
* using session charset: ISO8859-1
* checking for file 'moduleColor/DESCRIPTION' ... OK
* this is package 'moduleColor' version '1.08-1'
* 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 whether package 'moduleColor' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for portable file names ... 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
* loading checks for arch 'i386'
** 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
* loading checks for arch 'x64'
** 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 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 'moduleColor/R/Functions.R':
  .onLoad calls:
    cat(paste("Package moduleColor, version", .moduleColorOptions$version,     "revision date", .moduleColorOptions$revisionDate, "\n"))
    cat(paste("  Active module eigengene name prefix:", .moduleColorOptions$MEprefix,     "\n"))

Package startup functions should use 'packageStartupMessage' to
  generate messages.
See section 'Good practice' in ?.onAttach.

multiSetMEs: warning in moduleEigengenes(expr = exprData[[set]]$data,
  color = setColors, impute = impute, nPC = nPC, align = align,
  excludeGrey = excludeGrey, grey = grey, trapErrors = trapErrors,
  subHubs = subHubs, returnValidOnly = FALSE, softPower = softPower,
  verbose = verbose - 1, indent = indent + 1): partial argument match
  of 'color' to 'colors'
multiSetMEs: warning in moduleEigengenes(expr = exprData[[set]]$data[,
  useGenes], color = setColors, impute = impute, nPC = nPC, align =
  align, excludeGrey = excludeGrey, grey = grey, trapErrors =
  trapErrors, subHubs = subHubs, returnValidOnly = FALSE, softPower =
  softPower, verbose = verbose - 1, indent = indent + 1): partial
  argument match of 'color' to 'colors'
* 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 examples ...
** running examples for arch 'i386' ... OK
** running examples for arch 'x64' ... OK
* checking PDF version of manual ... OK
NOTE: There was 1 note.
See
  'd:/Rcompile/CRANpkg/local/2.15/moduleColor.Rcheck/00check.log'
for details.