• using R Under development (unstable) (2012-02-23 r58468)
• using platform: i686-pc-linux-gnu (32-bit)
• using session charset: UTF-8
• checking for file ‘relevent/DESCRIPTION’ ... OK
• this is package ‘relevent’ version ‘1.0’
• 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 ‘relevent’ 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 ‘relevent/R/zzz.R’:
  .onLoad calls:
  cat(paste("'", ehelp[4], "'\n", "Version ", ehelp[2], " created on ", ehelp[3], ".\n", sep = ""))
  cat(paste(substring(ehelp[4], first = 16), "\n", "Version ", substring(ehelp[2], first = 16), " created on ", substring(ehelp[3], first = 16), ".\n", sep = ""))
  cat(paste("copyright (c) 2007, Carter T. Butts, University of California-Irvine\n", sep = ""))
  cat("Type help(package=\"relevent\") to get started.\n")
  
  Package startup functions should use ‘packageStartupMessage’ to
  generate messages.
  See section ‘Good practice’ in ?.onAttach.
  
  accum.ps: warning in matrix(.Call("accum_ps_R", elist, PACKAGE =
  "relevent"), nc = 13): partial argument match of 'nc' to 'ncol'
  print.summary.rem: warning in matrix(x$coef, nc = 1): partial argument
  match of 'nc' to 'ncol'
  print.summary.rem.dyad: warning in matrix(x$coef, nc = 1): partial
  argument match of 'nc' to 'ncol'
  rem: warning in matrix(nr = clen * mcmc.chains, nc = np): partial
  argument match of 'nr' to 'nrow'
  rem: warning in matrix(nr = clen * mcmc.chains, nc = np): partial
  argument match of 'nc' to 'ncol'
  rem: warning in matrix(nr = clen, nc = np): partial argument match of
  'nr' to 'nrow'
  rem: warning in matrix(nr = clen, nc = np): partial argument match of
  'nc' to 'ncol'
  rem: warning in sample(1:NROW(draws), sir.draws, rep = TRUE, prob =
  exp(iw)): partial argument match of 'rep' to 'replace'
  rem.dyad: warning in matrix(temp$predicted, nc = 2): partial argument
  match of 'nc' to 'ncol'
  rem.dyad: warning in sample(1:NROW(post), sir.draws, rep = TRUE, prob =
  exp(iw)): partial argument match of 'rep' to 'replace'
• 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 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 ... [0s/0s] OK
• checking PDF version of manual ... OK
  NOTE: There was 1 note.
  See
  ‘/home/hornik/tmp/R.check/r-devel/Work/PKGS/relevent.Rcheck/00check.log’
  for details.