• using R Under development (unstable) (2012-08-11 r60235)
• using platform: x86_64-unknown-linux-gnu (64-bit)
• using session charset: UTF-8
• using options ‘--no-examples --no-tests --no-vignettes’
• checking for file ‘fields/DESCRIPTION’ ... OK
• this is package ‘fields’ version ‘6.6.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 for executable files ... OK
• checking for hidden files and directories ... OK
• checking whether package ‘fields’ 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 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
  sreg: warning in gcv.sreg(out, lambda = lam, cost = cost, offset =
  offset, nstep.cv = nstep.cv, verbose = verbose, trmin = trmin, trmax
  = trmax, rmse = rmse): partial argument match of 'lambda' to
  'lambda.grid'
  in.land.grid: no visible binding for global variable ‘world.dat’
  world.land: no visible binding for global variable ‘world.dat’
• 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 'fields internal':
  ‘image.plot.info’ ‘image.plot.plt’ ‘summary.gcv.Krig’
  ‘summary.gcv.sreg’
  
  S3 methods shown with full name in documentation object 'image.plot':
  ‘image.plot’
  
  S3 methods shown with full name in documentation object 'image.smooth':
  ‘image.smooth’
  
  S3 methods shown with full name in documentation object 'predict.derivative':
  ‘predict.derivative’
  
  S3 methods shown with full name in documentation object 'predict.se':
  ‘predict.se’
  
  S3 methods shown with full name in documentation object 'predict.surface':
  ‘predict.surface’ ‘predict.surface.se’ ‘predict.surface.derivative’
  
  S3 methods shown with full name in documentation object 'vgram.matrix':
  ‘plot.vgram.matrix’
  
  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 line endings in C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking compiled code ... OK
• checking examples ... SKIPPED
• checking for unstated dependencies in tests ... OK
• checking tests ... SKIPPED
• checking PDF version of manual ... OK
  NOTE: There were 2 notes.
  See
  ‘/home/hornik/tmp/R.check/r-devel/Work/PKGS/fields.Rcheck/00check.log’
  for details.