• using R version 2.14.2 (2012-02-29)
  • using platform: i386-pc-mingw32 (32-bit)
  • using session charset: ISO8859-1
  • checking for file 'FunNet/DESCRIPTION' ... OK
  • this is package 'FunNet' version '1.00-12'
  • checking package dependencies ... OK
  • checking if this is a source package ... OK
  • checking if there is a namespace ... NOTE
    As from R 2.14.0 all packages need a namespace.
    One will be generated on installation, but it is better to handcraft a
    NAMESPACE file: R CMD build will produce a suitable starting point.
  • checking whether package 'FunNet' can be installed ... OK
  • checking installed package size ... NOTE
    installed size is 6.5Mb
    sub-directories of 1Mb or more:
    R 5.0Mb
    data 1.4Mb
  • 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
    File 'FunNet/R/FunNet.R':
    .First.lib calls:
    cat(paste("\nThis is FunNet package ", .funnet.version, " built and maintained by Corneliu Henegar.\n", "Using Gene Ontology and KEGG annotations updated on ", annot.date, ".\n\n", "FunNet(wd='', org=c('hsa','mmu','rno','sce','gga','ath','dre','cel','dme'), two.lists=TRUE, up.frame=NULL,\n", "\t genes.frame=NULL, restrict=FALSE, ref.list=NULL, logged=FALSE,\n", "\t down.frame=NULL, discriminant=FALSE, go.bp=TRUE, go.cc=TRUE, go.mf=TRUE,\n", "\t kegg=TRUE, annot.method=c('specificity','terminological','decorrelated'),\n", "\t annot.details=TRUE, direct=FALSE, enriched=TRUE, fdr=5, build.annot.net=TRUE,\n", "\t coexp.matrix=NULL, coexp.method=c('spearman','pearson','kendall','euclid'),\n", "\t estimate.th=FALSE, hard.th=NA, soft.th=NA, topological = FALSE, keep.sign=FALSE,\n", "\t level=NA, annot.clust.method=c('umilds','ucknn'), annot.prox.measure=c('dynamical',\n", "\t 'unilat.pond.norm.mean','unilat.norm.sum','norm.sum','pond.norm.mean'),\n", "\t test.recovery=FALSE, test.robust=FALSE, replace.annot=NA,random.annot=FALSE,\n", "\t build.gene.net=FALSE, gene.clust.method='hclust', gene.net.details=FALSE,\n", "\t gene.clusters=NA, alpha=0.05, RV=0.90, sigma=NA, keep.rdata=FALSE, zip=TRUE)\n\n", sep = ""))

    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 ... OK
  • 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 R/sysdata.rda ... OK
  • checking examples ... OK
  • checking PDF version of manual ... OK