* using log directory 'd:/Rcompile/CRANpkg/local64/2.11/seas.Rcheck'
* using R version 2.11.1 Patched (2010-07-29 r52657)
* using session charset: ISO8859-1
* checking for file 'seas/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'seas' version '0.3-9'
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking whether package 'seas' can be installed ... 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 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
getstnname: no visible binding for global variable 'mscstn'
* 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.seas.temp':
  plot.seas.temp

S3 methods shown with full name in documentation object 'plot.seas.var':
  plot.seas.var

S3 methods shown with full name in documentation object 'plot.year':
  plot.year

The \usage entries for S3 methods should use the \method markup and not
their full name.
See the chapter 'Writing R documentation files' in manual 'Writing R
Extensions'.
* checking Rd contents ... OK
* checking data for non-ASCII characters ... WARNING
  Warning: found non-ASCII string(s)
  '<c2><b0>C'
Portable packages use only ASCII characters in their datasets.
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking for portable use of $BLAS_LIBS ... OK
* checking examples ... OK
* checking PDF version of manual ... OK