CRAN Package Check Results for Package liso

Last updated on 2018-05-03 10:50:59 CEST.

Check Details

Version: 0.2
Check: for hidden files and directories
Result: NOTE
    Found the following hidden files and directories:
     .DESCRIPTION.swo
    These were most likely included in error. See section ‘Package
    structure’ in the ‘Writing R Extensions’ manual.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-ix86+x86_64, r-patched-linux-x86_64, r-patched-solaris-x86, r-release-linux-x86_64, r-release-windows-ix86+x86_64, r-release-osx-x86_64, r-oldrel-windows-ix86+x86_64, r-oldrel-osx-x86_64

Version: 0.2
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     Note: next used in wrong context: no loop is visible
    See ‘/home/hornik/tmp/R.check/r-devel-clang/Work/PKGS/liso.Rcheck/00install.out’ for details.
    Information on the location(s) of code generating the ‘Note’s can be
    obtained by re-running with environment variable R_KEEP_PKG_SOURCE set
    to ‘yes’.
Flavor: r-devel-linux-x86_64-debian-clang

Version: 0.2
Check: DESCRIPTION meta-information
Result: NOTE
    Malformed Description field: should contain one or more complete sentences.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-ix86+x86_64, r-patched-linux-x86_64, r-patched-solaris-x86, r-release-linux-x86_64, r-release-windows-ix86+x86_64, r-release-osx-x86_64, r-oldrel-windows-ix86+x86_64, r-oldrel-osx-x86_64

Version: 0.2
Check: dependencies in R code
Result: NOTE
    Packages in Depends field not imported from:
     ‘Iso’ ‘MASS’
     These packages need to be imported from (in the NAMESPACE file)
     for when this namespace is loaded but not attached.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-ix86+x86_64, r-patched-linux-x86_64, r-patched-solaris-x86, r-release-linux-x86_64, r-release-windows-ix86+x86_64, r-release-osx-x86_64, r-oldrel-windows-ix86+x86_64, r-oldrel-osx-x86_64

Version: 0.2
Check: S3 generic/method consistency
Result: NOTE
    Found the following apparent S3 methods exported but not registered:
     seq.log
    See section ‘Registering S3 methods’ in the ‘Writing R Extensions’
    manual.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64, r-patched-solaris-x86, r-release-linux-x86_64

Version: 0.2
Check: R code for possible problems
Result: NOTE
    ave.sorted: warning in matrix(y[lens == i], nr = i): partial argument
     match of ‘nr’ to ‘nrow’
    ave.sorted: warning in matrix(weights[lens == i], nr = i): partial
     argument match of ‘nr’ to ‘nrow’
    liso.adaptive: warning in multistep(coefc = rep(0, (nrow(x) - 1) *
     ncol(x)), x = x, intercept = sum(weights * y)/sum(weights), residual
     = y - sum(weights * y)/sum(weights), sorter = getSort(x)): partial
     argument match of ‘coefc’ to ‘coefchain’
    liso.backfit: warning in multistep(coefc = rep(0, (nrow(x) - 1) *
     ncol(x)), x = x, intercept = sum(weights * y)/sum(weights), residual
     = y - sum(weights * y)/sum(weights), sorter = getSort(x)): partial
     argument match of ‘coefc’ to ‘coefchain’
    &.multistep : addup: no visible global function definition for ‘approx’
    cv.liso: no visible global function definition for ‘tail’
    cv.liso: no visible binding for global variable ‘var’
    error.bars: no visible global function definition for ‘segments’
    liso.maxlamb: no visible global function definition for ‘pava’
    objsort : <anonymous>: no visible global function definition for
     ‘object.size’
    pavareg: no visible global function definition for ‘pava’
    pavaregorig: no visible global function definition for ‘pava’
    plot.multistep: no visible global function definition for ‘par’
    plot.multistep: no visible global function definition for ‘tail’
    plot.multistep: no visible global function definition for ‘plot’
    plot.multistep: no visible global function definition for ‘lines’
    plot.multistep: no visible global function definition for ‘title’
    plot.multistep: no visible global function definition for ‘points’
    plotCV: no visible global function definition for ‘plot’
    repeatplot: no visible global function definition for ‘plot’
    repeatplot: no visible global function definition for ‘lines’
    repeatplot: no visible global function definition for ‘points’
    Undefined global functions or variables:
     approx lines object.size par pava plot points segments tail title var
    Consider adding
     importFrom("graphics", "lines", "par", "plot", "points", "segments",
     "title")
     importFrom("stats", "approx", "var")
     importFrom("utils", "object.size", "tail")
    to your NAMESPACE file.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-ix86+x86_64, r-patched-linux-x86_64, r-patched-solaris-x86, r-release-linux-x86_64, r-release-windows-ix86+x86_64, r-release-osx-x86_64, r-oldrel-windows-ix86+x86_64, r-oldrel-osx-x86_64

Version: 0.2
Check: Rd line widths
Result: NOTE
    Rd file 'cv.liso.Rd':
     \usage lines wider than 90 characters:
     cv.liso(x, y, K = 10, lambda = NULL, trace = FALSE, plot.it = FALSE, se = TRUE, weights = rep(1, length(y)), weightedcv = FALSE, huber ... [TRUNCATED]
    
    Rd file 'liso.Rd':
     \usage lines wider than 90 characters:
     liso(x, y, adaptive = TRUE, lambda = NULL, monotone = NULL, control=list(cv = NULL, liso = NULL ))
     \examples lines wider than 100 characters:
     ## Do an adaptive fit constrained to be monotone increasing, with an increased tolerance for convergence in the crossvalidation
    
    Rd file 'liso.backfit.Rd':
     \usage lines wider than 90 characters:
     liso.backfit(x, y, lambda=0, givebeta = FALSE, tol.target = 1e-04, weights= rep(1, length(y)), covweights=rep(1, ncol(x)), feed, trace= ... [TRUNCATED]
    
    Rd file 'liso.covweights.Rd':
     \examples lines wider than 100 characters:
     secondfit = liso.backfit(x,y2, 2, monotone=FALSE, covweights = liso.covweights(initialfit, signfind=TRUE))
    
    Rd file 'liso.maxlamb.Rd':
     \usage lines wider than 90 characters:
     liso.maxlamb(x=NULL,y=NULL,monotone=TRUE, covweights=rep(1, ncol(x)), weights=rep(1, length(y)))
    
    Rd file 'multistep.Rd':
     \usage lines wider than 90 characters:
     multistep(coefchain,x=NULL,intercept=0,sortedx = apply(x,2,sort),names = NULL, pinters=NULL,...)
    
    Rd file 'plot.multistep.Rd':
     \usage lines wider than 90 characters:
     plot(x = NULL, xpoints=NULL, ypoints = NULL, dims = 1:max(nrow(x$param), ncol(xpoints)) , ylimit = cbind(min(min(x),max(x)), max(max(x) ... [TRUNCATED]
    
    These lines will be truncated in the PDF manual.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64, r-release-linux-x86_64

Version: 0.2
Check: Rd \usage sections
Result: NOTE
    S3 methods shown with full name in documentation object 'seq.log':
     ‘seq.log’
    
    The \usage entries for S3 methods should use the \method markup and not
    their full name.
    See chapter ‘Writing R documentation files’ in the ‘Writing R
    Extensions’ manual.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-ix86+x86_64, r-patched-linux-x86_64, r-patched-solaris-x86, r-release-linux-x86_64, r-release-windows-ix86+x86_64, r-release-osx-x86_64, r-oldrel-windows-ix86+x86_64, r-oldrel-osx-x86_64

Version: 0.2
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     Note: next used in wrong context: no loop is visible
    See ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/PKGS/liso.Rcheck/00install.out’ for details.
    Information on the location(s) of code generating the ‘Note’s can be
    obtained by re-running with environment variable R_KEEP_PKG_SOURCE set
    to ‘yes’.
Flavor: r-devel-linux-x86_64-debian-gcc

Version: 0.2
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     Note: next used in wrong context: no loop is visible
    See ‘/data/gannet/ripley/R/packages/tests-clang/liso.Rcheck/00install.out’ for details.
    Information on the location(s) of code generating the ‘Note’s can be
    obtained by re-running with environment variable R_KEEP_PKG_SOURCE set
    to ‘yes’.
Flavor: r-devel-linux-x86_64-fedora-clang

Version: 0.2
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     Note: next used in wrong context: no loop is visible
    See ‘/data/gannet/ripley/R/packages/tests-devel/liso.Rcheck/00install.out’ for details.
    Information on the location(s) of code generating the ‘Note’s can be
    obtained by re-running with environment variable R_KEEP_PKG_SOURCE set
    to ‘yes’.
Flavor: r-devel-linux-x86_64-fedora-gcc

Version: 0.2
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     Note: next used in wrong context: no loop is visible
    See 'd:/Rcompile/CRANpkg/local/3.5/liso.Rcheck/00install.out' for details.
    Information on the location(s) of code generating the 'Note's can be
    obtained by re-running with environment variable R_KEEP_PKG_SOURCE set
    to 'yes'.
Flavors: r-devel-windows-ix86+x86_64, r-release-windows-ix86+x86_64

Version: 0.2
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     Note: next used in wrong context: no loop is visible
    See ‘/home/hornik/tmp/R.check/r-patched-gcc/Work/PKGS/liso.Rcheck/00install.out’ for details.
    Information on the location(s) of code generating the ‘Note’s can be
    obtained by re-running with environment variable R_KEEP_PKG_SOURCE set
    to ‘yes’.
Flavor: r-patched-linux-x86_64

Version: 0.2
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     Note: next used in wrong context: no loop is visible
    See ‘/home/ripley/R/packages/tests32/liso.Rcheck/00install.out’ for details.
    Information on the location(s) of code generating the ‘Note’s can be
    obtained by re-running with environment variable R_KEEP_PKG_SOURCE set
    to ‘yes’.
Flavor: r-patched-solaris-x86

Version: 0.2
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     Note: next used in wrong context: no loop is visible
    See ‘/home/hornik/tmp/R.check/r-release-gcc/Work/PKGS/liso.Rcheck/00install.out’ for details.
    Information on the location(s) of code generating the ‘Note’s can be
    obtained by re-running with environment variable R_KEEP_PKG_SOURCE set
    to ‘yes’.
Flavor: r-release-linux-x86_64

Version: 0.2
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     Note: next used in wrong context: no loop is visible
    See ‘/Volumes/SSD-Data/Builds/R-dev-web/QA/Simon/packages/el-capitan-x86_64/results/3.5/liso.Rcheck/00install.out’ for details.
    Information on the location(s) of code generating the ‘Note’s can be
    obtained by re-running with environment variable R_KEEP_PKG_SOURCE set
    to ‘yes’.
Flavor: r-release-osx-x86_64