* using log directory 'd:/Rcompile/CRANpkg/local/2.14/spectralGP.Rcheck'
* using R version 2.14.2 (2012-02-29)
* using platform: i386-pc-mingw32 (32-bit)
* using session charset: ISO8859-1
* checking for file 'spectralGP/DESCRIPTION' ... OK
* this is package 'spectralGP' version '1.3'
* 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 'spectralGP' 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
* 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 'spectralGP/R/onLoad.R':
  .onLoad calls:
    cat("Package spectralGP (1.3) is loaded.\n===============================================================\n WARNING: spectralGP uses objects in the form of environments,\n thereby passing by reference.  Various method functions make\n changes to the input gp object as a side effect, thereby\n changing the object in the calling environment, and\n returning NULL.\n===============================================================",     fill = FALSE)

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 ... NOTE
S3 methods shown with full name in documentation object 'image.plot':
  'image.plot'

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 examples ... OK
* checking PDF version of manual ... OK