search for: cachesweave

Hello all, I would like to ask several questions regarding cacheSweave: 1) Is there a way to set "cache=true" globally? (I tried it using \SweaveOpts but it didn't seem to work) 2) Is there a way to "flush" specific cache once it is created? (other then erasing the entire cache directory)? Changing the code in the code chunk seems to do it, b...

It's been a while since this thread appeared, but I had the same problem and don't want to keep the solution for myself. A small, reproducible example: <<cache=true>>= a=1 @ <<>>= a+1 @ Compiling with cacheSweave gives an error: > library(cacheSweave) Lade n?tiges Paket: filehash filehash: Simple key-value database (2.0-1 2008-12-19) Lade n?tiges Paket: stashR A Set of Tools for Administering SHared Repositories (0.3-3 2009-03-26) > Sweave("cacheSweaveExample.rnw", driver=cacheSweaveDrive...

Dear All, I have been using Sweave (mainly via the Sweave.sh script) and really like it. I am working a paper (using Sweave, of course) which includes several time-consuming computations, and it gets tedious to re-compile the whoel thing every time I made changes. Then I discover the "cacheSweave" package, which seems the right solution to my problem. I only have on problem. Here is what I did: ---------------------------------------------- <<results=hide,echo=false>>= library(foreign) library(Zelig) library(memisc) options(digits=4) @ <<echo=false>>= d <-...

This could well be a package-specific issue, and so perhaps not for R-devel. The author of the relevant package is CC'd in any event. I'm seeing some odd behavior from Sweave with keep.source=TRUE when using driver=cacheSweaveDriver from the cacheSweave package. It would seem that code chunks with keep.source=TRUE aren't being parsed correctly; the corresponding Schunk starts at the *very top* of the Rnw file, snippet shown below. The error seems specific to R 2.12.0; cacheSweave + keep.source=TRUE seems to work o...

Dear all, When I use the cacheSweave package together with the Sweave option keep.source = TRUE, all the LaTeX code before the Sweave code chunk is included in the TeX file to be compiled. For example, with the following Sweave file \documentclass[12pt]{article} \usepackage[nogin]{Sweave} % Sweave options \SweaveOpts{keep.source=TRU...

Hi all, I use the excellent packages rjags and cacheSweave, and unfortunately seem to have found an incompatibility between them. Below are a minimal .Rnw file and corresponding JAGS model file which illustrate the problem: *** JAGS model file; name=j.bug *** model { mu ~ dnorm(0,1.0E-5) sigma ~ dunif(0,100) for(i in 1:length(y)) { y[...

Hi there I have a problem with using Sweave in combination with the option driver = cacheSweave. Whichever code I try to run - when it comes to converting the tex file into pdf it comes up with the same errors (\csname \endcsname errors). Does anybody have an idea what it going wrong? > Sweave("pgfSweave-example.Rnw",driver = cacheSweaveDriver) Writing to file pgfSweave-exam...

Dear list, I wish to use a specific driver to process an sweave document in the inst/doc directory of a package. Specifically, I would like to use either cacheSweave or pgfSweave to speed up the creation of the vignette which requires lengthy computations. The same request would also apply to the highlight driver, to provide syntax highlighting of R chunks. In "writing R extensions" I see that during R CMD BUILD Sweave is run first, then optionally a...

Dear list, I wish to use a specific driver to process an sweave document in the inst/doc directory of a package. Specifically, I would like to use either cacheSweave or pgfSweave to speed up the creation of the vignette which requires lengthy computations. The same request would also apply to the highlight driver, to provide syntax highlighting of R chunks. In "writing R extensions" I see that during R CMD BUILD Sweave is run first, then optionally a...

At long last pgfSweave has finally made its way to CRAN. The pgfSweave package is about speed and style of graphics. For speed, the package provides capabilities for ?caching? graphics generated with Sweave on top of the caching funcitonality of cacheSweave. For style the pgfSweave package facilitates the integration of R graphics with LaTeX reports through the tikzDevice package and eps2pgf utility. With these tools, figure labels are converted to LaTeX strings so they match the style of the document and the full range of LaTeX math symbols/equations...

At long last pgfSweave has finally made its way to CRAN. The pgfSweave package is about speed and style of graphics. For speed, the package provides capabilities for ?caching? graphics generated with Sweave on top of the caching funcitonality of cacheSweave. For style the pgfSweave package facilitates the integration of R graphics with LaTeX reports through the tikzDevice package and eps2pgf utility. With these tools, figure labels are converted to LaTeX strings so they match the style of the document and the full range of LaTeX math symbols/equations...

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 overlooking something obvious. Below is my .Rnw and sessionInfo. Pointers, suggestions, etc are most welcome. %%%%%%%%%%%%%%% RNW;...

Does anybody have a workable system to run an Rnw document through R-Sweave when necessary, but to just run it through LaTeX if no new R calculations are needed? I.e., the figures already exist, I do not need R to do more work for me, so I send the document straight to LaTeX. I want to leave open the option that I might need to run the document through Sweave in the future, so I don't want

Dear R-helpers, I would like the bands in an xYplot() to be gray without dark edges. I've tried playing around with col.bands, but that seems not to affect the edges, although changin col.fill does change the fill as I would expect. I would appreciate pointers. _____________________________ Professor Michael Kubovy University of Virginia Department of Psychology USPS: P.O.Box

Dear R user, I am using Sweave to write my reports with R code. Unlucly my code take a lot of time to run, and I don't want to run it multiple time, if possible, as I am still developping the tools. It seems that a sweave run does not save the enviroment at the end of the process, is there a way to avoid to lunch multiple time the same commands? maybe it could be possible to store chunck of

hello: Do any one know how to set sweave option by variable, for example I want set some of my selected code chunk with: <<eval=needRun>>= rather than <<eval=TRUE>>=, so I can change the action only in the head by change the variable "needRun" one times. I have tried use "\Def" and "\newcommand", both do not work, so I suppose it is related

Hello everybody out there using Sweave, There are some complicated SQL queries and laborous calculations against large data included as R code chunks using Sweave in my LaTeX document. These code chunks create graphs that do not change most of the time, but they are of course recompiled every time I run Sweave on my file for update of minor changes to the LaTeX text. Is there an option

Dear All I am preparing a number of vignettes that require a very long time to process with Sweave. The longest one takes 10 hours. I love the weaver package! Is a package that includes such a computationally intensive vignette acceptable on CRAN? Are there any guidelines here? -- Robin K. S. Hankin Uncertainty Analyst University of Cambridge 19 Silver Street Cambridge CB3 9EP

...ess the relevant R core members were not there (presumably Fritz, Duncan and Brian), so I'm making this wishlist again: Currently package vignettes have to be processed through Sweave, which is too restrictive since several add-on packages aiming to improve or extend Sweave have appeared (e.g. cacheSweave, pgfSweave, R.rsp, highlight, knitr, ...). The common hack that package authors use, as far as I can see, is the Makefile. One example is at https://github.com/yihui/knitr/blob/master/inst/doc/Makefile Although this hack works well for some cases, it is potentially problematic in two aspects: 1....

...n8.9.1 locale: C attached base packages: [1] "grDevices" "datasets" "grid" "graphics" "stats" "utils" [7] "methods" "base" other attached packages: coda lme4 Matrix car cacheSweave stashR "0.10-7" "0.9975-13" "0.9975-11" "1.2-1" "0.3" "0.2-1" filehash digest circular boot gmodels multcompView "0.9-4" "0.2.3" "0.3-6&...