similar to: parse_Rd and/or lazyload problem

There is a bug in `predict' whereby the order of variables sometimes gets re-arranged compared to the original fit, and then disaster results. Specifically, the 'variables' and 'predvars' attributes of a 'terms' object get out of synch. This only happens when the terms in the original formula get re-ordered during fitting: test> scrunge.data_ data.frame(

# r-bugs@r-project.org `predict' complains about new factor levels, even if the "new" levels are merely levels in the original that didn't occur in the original fit and were sensibly dropped, and that don't occur in the prediction data either. (At least if `drop.unused.levels' was set to TRUE, which the default.) test> scrunge.data.2_ data.frame( y=runif( 3),

I'm developing an R package, and when I recompile (using Roxygen), detach, and re-load the package, I can't seem to look at some of its documented functions. When I try '?function.name', I get the following error: Error in tools:::fetchRdDB(RdDB, basename(file)) : cannot allocate memory block of size 2.6 Gb I'm using R.app's built-in documentation viewer. I

I was writing Rd documentation for a new package when I came across this issue. Here's the smallest example: > library(tools) > cat("\\examples{x <- '<%=rnorm(1)%>'}\n",file=file.path(tempdir(),'test.Rd')) > readLines(file.path(tempdir(),'test.Rd')) [1] "\\examples{x <- '<%=rnorm(1)%>'}" >

Hi, I need some help with 2.9.0 parse_Rd() Version 2 changes. I read the .pdf file and some posts on r-help, but after playing with this for several hours, I can't seem to get around this UTF-8 problem. - I'm trying to get rid of some warnings during R CMD Check for R 2.9.0Alpha on Japanese Vista 32 - The same setup on a R 2.9.0Alpha English XP Pro 32 works fine without any

Hi R-devels, I noticed that you are working quite actively on the new Rd-parser and have made it the default renderer in R-2.10.0dev. So I would like to come back on an issue I have already raised on this list last November ("Two minor escaping issues using \preformatted{....} in Rd format") My setting has slightly changed as \preformatted, AFAICS is not supported within \describe

R-developers, I have a binary R package built using R 2.14.1 that I would like to run on R 3.0.0. Unfortunately, the original source code is unavailable, so I cannot rebuild the package as R 3.0.0 requires. Is there a straight forward way of converting the package (.rdb, .rdx and .rds files) in the binary package from a 2.14.1 version to a 3.0.0 version without the source code (perhaps

Full_Name: Ross Boylan Version: 2.10.0 OS: Windows XP Submission from: (NULL) (198.144.201.14) Some of the help for setGeneric seems to have been garbled. In the section "Basic Use", 5th paragraph (where the example counts as a single line 3rd paragraph) it says <quote> Note that calling 'setGeneric()' in this form is not strictly necessary before calling

Under R2.10.0 beta (2009-10-14 r50082) my .First does not run reliably. I reported this last week, but not reproducibly, and it seemed to go away, so I thought it might be installation-related. But it has now recurred reproducibly, at least on my machine. The website ftp://ftp.csiro.au/MarkBravington contains two .RData files each containing (only) a .First. One of them does what it should, and

On 2015-12-18 02:29, Simon Urbanek wrote: > Michael, > > I got access to PDP AIX so I can try to replicate your problem. Can you, please, share exactly your setup - AIX version and well as how exactly you installed the compilers (=where from)? I can then try to replicate it. AFAICS there is no official binary for gfortran nor gcc 4.7 so it must be some 3rd party - which could also be a

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 +++

> 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() automatically without explicitly having to load() each

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

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, 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

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

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",

When I run R CMD Rd2pdf on the man pages of a package, ie R CMD Rd2pdf man I get Converting Rd files to LaTeX Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, : man/mpra-package.Rd:6: unknown macro '\packageTitle' Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, :

Bug or feature? I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, eg \mymacro{}: Error in tools::parse_Rd(fn) : Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but