search for: lazyload

Dear developeRs, I've searched the documentation, FAQ, and mailing lists, but haven't found the answer(*) to the following: When should one specify LazyLoad, LazyData, and ZipData? And what is the default if they are left unspecified? (*)Except that 1) If the package you are writing uses the methods package, specify LazyLoad: yes, and 2) The optional ZipData field controls whether the automatic Windows build will zip up the data directory or no: set...

...lazy data loading may have memory and performance advantages, but for the larger metaData packages the installation is painfully slow (it has taken > 30 min to install a large metaData package on a PIII, 933 MHz box running Mandrake 9.2). The vast majority of the time is spent moving datasets to lazyload DB. It takes a long time to build the win32 packages as well, but once the package is built, the installation is quick, so there is no real problem for our end users. So my question is this; is there a mechanism that can be used to pre-build the lazyload DB for source packages to decrease the inst...

Is there a global option somewhere that can completely disable the LazyLoad option? I want all my packages in source format for searching purposes, crippled by the conversion to database format. ---------------------------------------------------------- SIGSIG -- signature too long (core dumped)

Hi, On Windows, package files in the inst/ subdir are installed after the lazyload creation. This differs from Linux where inst/ is installed _before_ lazyload creation. Since packages may need data in inst, I think the order on Windows should be changed. Perhaps like this: diff --git a/src/gnuwin32/MakePkg b/src/gnuwin32/MakePkg index 57af321..868e8f1 100644 --- a/src/gnuwin...

...g strange errors while working on my caTools package: >RCMD install C:/programs/R/rw2011/src/library/caTools ...... preparing package caTools for lazy loading Error in file(file, "r", encoding = encoding) : all connections are in use Execution halted make: *** [lazyload] Error 1 *** Installation of caTools failed *** I searched through R website and mailing lists but did not found many clues. I am not running R environment so showConnections and CloseAllConnections functions are not helpful. Did I run into some OS specific limit on number of files allowed? I clo...

...check (WindowsXP home edition, rw2000dev, on a new toshiba laptop, if that matters.) but then Rcmd build --binary gives problems: . . . preparing package asypow for lazy loading Error in tools:::.read_description(file) : file '/DESCRIPTION' does not exist Execution halted make: *** [lazyload] Error 1 *** Installation of asypow failed *** Removing 'C:/DOCUME~1/HALVOR~1/LOCALS~1/Temp/Rbuild.852/asypow' ERROR * installation failed . . . but as it passed make check, DESCRIPTION obviuosly is there, so this must be symptoms of something else. Then, adding the line LazyLoad:...

> What is the benefit of lazyload DB in this circumstance? I don't see it > if your .rda files have one data object each and are compressed. The paradigm we have been following is to have all the environments saved in individual .rda files, so after loading the package they can be accessed with e.g., ls(), get(), mget()...

In DESCRIPTION if I set LazyLoad to 'yes' will data.table (for example) then be byte compiled for users who install the binary package from CRAN on Windows? This question is based on reading section 1.2 of this document : http://www.divms.uiowa.edu/~luke/R/compiler/compiler.pdf I've searched r-devel and Stack Overflow...

Hi, In the DESCRIPTION file the ByteCompile and LazyLoading arguments appear to accept any value. >From the manual the field should be a "logical field". However, authors interpret this in a variety of ways: unique(tools::CRAN_package_db()$ByteCompile) # [1] NA "TRUE" "yes" "true" "Yes" "n...

...d stamp to DESCRIPTION installing R files preparing package RtTestsEG1 for lazy loading Loading required package: RtTests ... [lost of lines removed] Loading required package: RtTests Error: evaluation nested too deeply: infinite recursion / options(expressions=)? Execution halted make[2]: *** [lazyload] Error 1 make[1]: *** [all] Error 2 make: *** [pkg-RtTestsEG1] Error 2 *** Installation of RtTestsEG1 failed *** After some digging in the Windows makefiles, I found out that changing the locale from "C" to "us" in the "lazyload" target of $R_HOME/src/gnuwin32/MakePkg...

I added a new data file, NLSY.RData, to a package that uses LazyData: Yes It passed R CRAN check and R CMD install worked w/o significant complaints. * installing to library 'C:/R/R-2.15.2/library' * installing *source* package 'heplots' ... ** R ** data ** moving datasets to lazyload DB ** demo ** inst ** preparing package for lazy loading Warning: package 'nnet' was built under R version 2.15.3 ** help ... Yet, when I try to use it, I get something incomprehensible: > library(heplots) > str(NLSY) Error in str(NLSY) : internal error -3 in R_decompress1 In ad...

Prior to R-3.6.0 the keys in the lazyload key files, e.g. pkg/data/Rdata.rdx or pkg/R/pkg.rdx, seemed to all be 2-long integer vectors. Now they can be lists. The ones I have seen have two components, "eagerKey" is a 2-long integer vector and "lazyKeys" is a named list of 2-long integer vectors. > rdx <- readRD...

...3107 osklyar at maninvestments.com --- pack1: DESCRIPTION ------ Package: pack1 Version: 0.0.1 Date: 12 Jan 2009 Title: pack1 to test S3/S4 methods compatibility Author: Oleg Sklyar Depends: R (>= 2.7.1), methods Maintainer: Oleg Sklyar <osklyar at maninvestments.com> Description: pack1 LazyLoad: yes License: Proprietary URL: http://www.maninvestments.com LazyLoad: no --- pack1: NAMESPACE ------ import(methods) exportPattern("^[^\\.]") exportClasses(posixTime) exportMethods(as.POSIXct) --- pack1: posix.R ------ setClass("posixTime", "numeric") setGeneric(&q...

Hi all, I'm struggling a bit to get pgfSweave to lazyload objects when compiling a .Rnw file for a second time. Caching works fine except that for every run all objects get cached again and again. I've used cacheSweave which works fine; all cached objects from code-chunks with option cache = TRUE are lazy loaded. I've tried it on two machines...

...preparing the package for lazy loading : preparing package pgirmess for lazy loading Error in "names<-.default"(`*tmp*`, value =c("R", "Platform", "Date", : names attribute[4] must be the same length as the vector [1] Execution halted make: ***[lazyload] Error 1 *** Installation of pgirmess failed *** (pgirmess is the package name) ... and the zip file is not generated. I have checked and rechecked everything during this (long) afternoon... and get nothing except that if I drag out any of the *.r file of the R folder, everything comes to be O...

From: Dirk Eddelbuettel <edd@debian.org> > I now have the package built in a chroot -- but at the price of setting > 'LazyLoad: no' in DESCRIPTION. > > I do not quite understand why that is needed. Can someone else help? I can > provide the following pointers for its-1.0.4 > I have had problems on Windows in which I had to pay the same price and it turned out that by using forward slashes rather than ba...

When I do a R CMD build --binary then I get the messages at the end of this post unless I specify LazyLoad: no in the DESCRIPRION file. If I do that then everything proceeds smoothly. R CMD check proceeds smoothly in either case. Is there something I should be aware of that is causing this message when I do not turn off lazy loading? I am using Windows XP and R 2.0.1 beta dated 2004-11-04. Erro...

...re attaching or installing the package may change in the near future. With the other facilities available as from R 2.0.0 they should be removed if possible. Every usage of these on CRAN is unnecessary. If you want to save the image, say so in the SaveImage field in DESCRIPTION (but why not LazyLoad instead?). If you require methods, say so in Depends in DESCRIPTION. I propose that we deprecate/remove this mechanism (as it makes installation a lot convoluted than it needs to be). Does any one know of (a) A usage that requires one of these files to do something which cannot now be done m...

Dear all, [I work with a Windows XP Prof. installation, and the 2.0.0 R version] I need to use the aws package, but I have the following error message: > require(aws) Loading required package: aws Error in firstlib(which.lib.loc, package) : couldn't find function "lazyLoad" [1] FALSE I download the .zip file (for Windows) today on the CRAN site, so I think I have an update version; does someone has already encountered this problem, do I miss something ? Thanks a lot for your help, Florence. [[alternative HTML version deleted]]

...will install on R v2.0.0 as well as Rv1.9.1, or do I "have to" provide two seperate builds? As you already know, current status is that building under R v2.0.0 and loading in R v1.9.1 gives the error: Error in firstlib(which.lib.loc, package) : couldn't find function "lazyLoad" In addition: Warning message: package R.oo was built under R version 2.0.0 and building under R v1.9.1 and loading in R v2.0.0 gives the error: Error in library(R.oo) : 'R.oo' is not a valid package -- installed < 2.0.0? Just to give it a try, I tried to build the package under...