similar to: cacheSweave questions (usage and forward compatibility)

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

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=TRUE, strip.white=TRUE, eps=FALSE, pdf=TRUE} \begin{document}

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

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

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

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

I am trying to transition from Sweave to knitr, but there are a few things about customization of the appearence of R input and output that I did not get yet. Maybe somebody on the list can help me. In my Sweave presentations I used a slanted font for the R input and a normal font for the output, both in a small font. I also indented everything by an extra 2em. All this was achieved by the

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[i] ~ dnorm(mu,sigma) } } *** *** .Rnw

Hi, Maybe I'm missing the point here...but let's suppose you are working with "large" data sets and using functions that take a significant amount of time to run in R. I woulnd't like to run these functions every time I call Sweave("myfile.Rnw") within R. What is the "common" practice to use Sweave in these situations. I would just run the function once,

Hola a todos: Con la entrada de R 3.0 en Debian Sid me acabo de llevar la sorpresa de que pgfSweave ya no esta mantenido [0]. He intentado compilarlo pero depende de otros paquetes que también se encuentran en el archivo: highlight y parser. En concreto este último falla al compilar (y ahí se acaba el intento). Estaba utilizando pgfSweave por la facilidad para incluir gráficos en Tikz -sin

Hello: Changes in R seem to have broken the sos vignette, and I don't know how to fix it. The build on R-forge, "https://r-forge.r-project.org/R/?group_id=235&log=build_src&pkg=sos&flavor=patched", ends as follows: Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : Running 'texi2dvi' on 'sos.tex' failed. LaTeX

Me interesa este tema. Estoy empezando ahora a ver el tema de armar documentos directamente con R y no estoy seguro en dónde me centro. Por lo que veo sweave y knitr son las dos grandes alternativas (de echo, no se siquiera si no son compatibles o complementarias). Para quien arranca en este tema y que pretende continuar sobre el mismo, que recomiendan, arrancar por sweave o por knitr?

Hello, since 3 days now I try to get pgfSweave running using Eclipse + StatET. I created a super simple .Rnw file which can be viewed here: http://www.text-upload.com/read.php?id=147992&c=6441045 test.Rnw When I use sweave it works perfectly fine but when I use pgfSweave I get an error. The R output can be viewed here: http://www.text-upload.com/read.php?id=147995&c=3804886 R output

I am working with Sweave and would like to print out into my latex document the result of the R command version$platform So what I first tried in my .Rnw document was \Sexpr{print(version$platform)}. However, the output from this command is the string "x86_64-apple-darwin10.8.0" (without the quotes). This contains an underscore, which is a special character in tex and so I get an error

Hi everyone, I am using package knitr, FIRST TIME. I don't have access to RStudio. Read through Yihui's page, didn't find it helpful. Stuck on terms Rnw, GFM (GitHub Flavored Markdown). Never used Sweave, so the reference is not helping. Is there a simple step-by-step example WITHOUT RStudio? My question: What is the procedure? The documentation explains the functions, but does

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

Gracias por las respuestas La verdad es qeu estoy trabjando con Rstudio + Knitr, lo unico que en R studio le doy a crear nuevo Sweave, pero is me carga la libreria knitr. Solucioné el problema que os comenté, era por un fallo tonto, a la hora de poner datos$A, puse dats$A, es decir, le faltaba la o.... Ahora una duda que no se como resolver es la de los gráficos. No consigo reducir su tamaño...

Hola, reenvío un ejemplo de uso de knitr por si alguien quiere echarle un vistazo rápido. Saludos, Javier ----- Hola Por si es de tu interés te envio un documento del uso de knitr (tejiendo con R) que, me parece, supera con creces a Sweave. Para compilar el documento, que se llama eje.Rnw debe utilizarse: Rscript -e "library(knitr); knit2pdf('eje.Rnw')" Se puede ulizar

I haven't figured it out entirely, but it looks like there are a couple of small glitches with knitr-based vignettes and SweaveParseOptions. I posted the tarball of a package with a knitr vignette with (as far as I can tell) everything properly coded in the DESCRIPTION file (VignetteBuilder: knitr, Suggests: knitr) and the vignette itself (%\VignetteEngine{knitr::knitr}). When Windows