search for: lazyloading

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

Hi all, Bioconductor has several metaData packages that contain quite large data sets. In the past, these data were simply held in the /data directory of the package as .rda files and load()ed as needed. Converting to using 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

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/gnuwin32/MakePkg +++

Hi, I suddenly started getting 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

Hola! I got past the problems I asked about two days ago, thanks. No I am updating CRAN package asypow (the daily package check on CRAN gave warnings due to .Rd problems, fixed). Now it PASSED Rcmd 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

...ggested by > 200update.txt and `Writing R Extensions'? The slow examples I have seen > did not and so were wasting a lot of time preparing indices that could > have been supplied. > > The design expectation was that large data packages would supply an index > and not use lazyloading for datasets but use separate compressed dumps for > each object. If there is some reason to change that, please send an RFC > for the requirements and a design. > > Did this not occur during the alpha/beta period for 2.0.0 several months > ago or has something in BioC changed s...

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 history and have found questions and answers relating to R CMD

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" "no&q...

...ry(RtTests), there is no problem. I happen to have all this working under Linux, so I tracked down the difference. Turns out that under Linux the equivalent to the "lazyload" target is in "/usr/lib/R/bin/INSTALL" and the difference is in the argument passed to "tools:::makeLazyLoading". Under Linux the full package name with version number is used, i.e. "RtTests_0.1-1". Windows just uses "RtTests". So I managed to fix the problem by making Windows use the full package name in the "lazyload" target. I replaced tools:::makeLazyLoading(\"$...

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

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 <- readRDS(system.file(package="survival",

Dear List: Sorry for posting maybe a trivial question, but I have a basic understanding problem. If I have say pack1 and pack2, two R packages, and pack2 depends on and imports pack1 fully (as in the code below), is there a way to make all the functionality of pack1 available for the global and other environments (not only for the functions called from withing pack2) by loading pack2 only? I

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 ... I'm pretty sure I'm

Dear Lister, I work with R 2.0.1 and Windows XP, and meet a strange trouble trying to make a R package with a make-package.bat file John Fox has kindly provided (see detailed script below). I am working with it since some months with excellent results (I do'nt use compiled C code so far). Just adding a new function in the R directory today, when running make-package and thus excuting

...ay interfere with the LazyLoad > directive. But I just don't understand how something can work in > session with a controlling terminal, but fail in the chroot'ed batch > built. > > Comments would be highly welcome. But please speak very slowly when it comes > to S4 and LazyLoading matters. There is an article on Lazy Loading in R News you may wish to read. > > Thanks, Dirk > > > > On Tue, Dec 14, 2004 at 10:17:16PM -0600, Dirk Eddelbuettel wrote: > > Trying to build its_1.0.4 in a chroot environment to update the > > corresponding Debian...

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

R-exts says Both install.R and R_PROFILE.R should be viewed as experimental; the mechanism to execute code before 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

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

Hi, just in the process of updating my packages for R v2.0.0 and I have not had time to followed the R v2.0.0 discussions so maybe my questions have already been answered. A concern I have is that when creating packages they should be backward compatible with R v1.9.x for a while until all users and computers has migrated to R v2.0.x. It is pretty straightforward to setup my packages so that