• using R Under development (unstable) (2012-08-11 r60235)
• using platform: x86_64-unknown-linux-gnu (64-bit)
• using session charset: UTF-8
• checking for file ‘MFDA/DESCRIPTION’ ... OK
• this is package ‘MFDA’ version ‘1.1-1’
• 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.
  CRAN requires a NAMESPACE file for all submissions.
• checking for executable files ... OK
• checking for hidden files and directories ... OK
• checking whether package ‘MFDA’ 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 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
  Estep.tik: no visible binding for global variable ‘mu’
  Estep.tik: no visible binding for global variable ‘zeta’
  Estep.tik: no visible binding for global variable ‘varht’
  Estep.tik: no visible binding for global variable ‘pk’
• checking Rd files ... NOTE
  prepare_Rd: Estep.tik.Rd:50-52: Dropping empty section \examples
  prepare_Rd: Estep.tk.Rd:54-56: Dropping empty section \examples
  prepare_Rd: MFclust.compute.Rd:66-68: Dropping empty section \examples
  prepare_Rd: check.start.Rd:28-29: Dropping empty section \examples
  prepare_Rd: compute.M.all.Rd:62-63: Dropping empty section \examples
  prepare_Rd: compute.M.pk.Rd:36-38: Dropping empty section \seealso
  prepare_Rd: compute.M.pk.Rd:39-41: Dropping empty section \examples
  prepare_Rd: compute.center.Rd:48-50: Dropping empty section \examples
  prepare_Rd: compute.reject.Rd:39-40: Dropping empty section \seealso
  prepare_Rd: compute.reject.Rd:41-43: Dropping empty section \examples
  prepare_Rd: compute.weight.Rd:41-43: Dropping empty section \examples
  prepare_Rd: em.bic.Rd:41-44: Dropping empty section \examples
  prepare_Rd: em.clust.Rd:53-55: Dropping empty section \seealso
  prepare_Rd: em.clust.Rd:56-58: Dropping empty section \examples
  prepare_Rd: mkrandom.Rd:32: Dropping empty section \references
  prepare_Rd: mkrandom.Rd:33: Dropping empty section \examples
• 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 examples ... [10s/10s] OK
• checking PDF version of manual ... OK
  NOTE: There were 3 notes.
  See
  ‘/home/hornik/tmp/R.check/r-devel/Work/PKGS/MFDA.Rcheck/00check.log’
  for details.