- using R Under development (unstable) (2012-05-19 r59366)
- using platform: x86_64-unknown-linux-gnu (64-bit)
- using session charset: UTF-8
- checking for file ‘ivivc/DESCRIPTION’ ... OK
- this is package ‘ivivc’ version ‘0.1.5’
- checking package dependencies ... OK
- checking if this is a source package ... OK
- checking if there is a namespace ... WARNING
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 whether package ‘ivivc’ 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
File ‘ivivc/R/zzz.R’:
.First.lib calls:
cat("\n")
cat("\n")
cat("****************************************************************************\n")
cat("* *\n")
cat("* ivivc *\n")
cat("* v 0.1.5 *\n")
cat("* *\n")
cat("* In vitro-in vivo correlation (IVIVC) is defined as the correlation *\n")
cat("* between in-vitro drug dissolution and in-vivo drug absorption. *\n")
cat("* This package is used to develop and validate an IVIVC model. *\n")
cat("* The following steps will be conducted: *\n")
cat("* -> 1: Input/Edit In-vivo absorption data: IV, oral solution or IR drug *\n")
cat("* -> 2: Develop an IVIVC model: Fitting IV, Oral solution or IR drug *\n")
cat("* -> 3: Input/Edit In-vitro dissolution data and in-Vivo absorption *\n")
cat("* Data: ER drug with different release rates *\n")
cat("* -> 4: Develop an IVIVC model: Model Dependent Method *\n")
cat("* -> 5: Evaluate an IVIVC model: Prediction error *\n")
cat("* *\n")
cat("* Please type 'run()' to get started. *\n")
cat("* *\n")
cat("****************************************************************************\n")
Package startup functions should use ‘packageStartupMessage’ to
generate messages.
See section ‘Good practice’ in ?.onAttach.
ivivc_demo: warning in genoud(objfun, nvars = 2, max = FALSE, pop.size
= 30, max.generations = 20, wait.generations = 10, starting.value =
c(0.13, 20), BFGS = FALSE, print.level = 0, boundary.enforcement = 2,
Domains = matrix(c(0.01, 0.01, 100, 100), 2, 2), MemoryMatrix =
TRUE): partial argument match of 'starting.value' to
'starting.values'
- 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 examples ... NONE
- checking PDF version of manual ... OK
WARNING: There was 1 warning.
NOTE: There was 1 note.
See
‘/home/hornik/tmp/R.check/r-devel/Work/PKGS/ivivc.Rcheck/00check.log’
for details.