• using R version 2.14.0 (2011-10-31)
• using platform: i386-apple-darwin9.8.0 (32-bit)
• using session charset: ASCII
• checking for file 'ares/DESCRIPTION' ... OK
• this is package 'ares' version '0.7.2'
• 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 whether package 'ares' 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 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 'ares/R/zzz.r':
  .onLoad calls:
  require("utils", quietly = TRUE, warn.conflicts = FALSE)
  require("stats", quietly = TRUE, warn.conflicts = FALSE)
  require("foreign", quietly = TRUE, warn.conflicts = FALSE)
  require("gam", quietly = TRUE, warn.conflicts = FALSE)
  require("splines", quietly = TRUE, warn.conflicts = FALSE)
  require("gplots", quietly = TRUE, warn.conflicts = FALSE)
  cat("This is 'ares' library", ver, "\n", sep = " ")
  
  Package startup functions should not change the search path.
  Package startup functions should use 'packageStartupMessage' to
  generate messages.
  See section 'Good practice' in ?.onAttach.
  
  desc.vars: no visible binding for global variable
  '.ares.active.dataset'
  fit.core: no visible binding for global variable '.ares.active.dataset'
  fit.core: no visible binding for global variable '.ares.selection'
  fit.core: no visible binding for global variable '.weights'
  gen.holidays: no visible binding for global variable '.ares.selection'
  import.data: no visible binding for global variable 'savefile'
  l: no visible binding for global variable '.ares.selection'
  ma: no visible binding for global variable '.ares.selection'
  pdf.report: no visible binding for global variable 'doe'
  plot.event: no visible binding for global variable '.ares.selection'
  plot.fitted: no visible binding for global variable '.ares.selection'
  plot.pollutant: no visible binding for global variable
  '.ares.selection'
  plot.residuals: no visible binding for global variable
  '.ares.selection'
  plot.risk: no visible binding for global variable 'ticks'
  save.plot: no visible binding for global variable 'devSVG'
  sincos: no visible binding for global variable '.ares.selection'
  unload: no visible binding for global variable '.ares.active.dataset'
• 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 ... NOTE
  S3 methods shown with full name in documentation object 'plot.constinfo':
  'plot.constinfo'
  
  S3 methods shown with full name in documentation object 'plot.cook':
  'plot.cook'
  
  S3 methods shown with full name in documentation object 'plot.envelope':
  'plot.envelope'
  
  S3 methods shown with full name in documentation object 'plot.event':
  'plot.event'
  
  S3 methods shown with full name in documentation object 'plot.fitted':
  'plot.fitted'
  
  S3 methods shown with full name in documentation object 'plot.pacf':
  'plot.pacf'
  
  S3 methods shown with full name in documentation object 'plot.pollutant':
  'plot.pollutant'
  
  S3 methods shown with full name in documentation object 'plot.qq':
  'plot.qq'
  
  S3 methods shown with full name in documentation object 'print.summary':
  'print.summary'
  
  The \usage entries for S3 methods should use the \method markup and not
  their full name.
  See the chapter 'Writing R documentation files' in the 'Writing R
  Extensions' manual.
• 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 ... OK
• checking PDF version of manual ... OK
• elapsed time (check, wall clock): 1:16