search for: rweavelatex

...; > Note, as per that manual page, that the Sweave options 'height' and 'width' > affect the size of the PDF and EPS files created, but it is the above > command that controls the size of the image in the document itself. > Could this information be incorporate into the RweaveLatex help page? Concerning the sizes of graphs, it contains only the following information: " width: numeric (6), width of figures in inches. height: numeric (6), height of figures in inches. " Unfortunately this concise information can easily mislead into believing that these two op...

Dear All, I have both R 2.80 and Scientific Workplace 5.5 installed on my computer. I copied the following commands from HTML help provided by R: testfile <- system.file("Sweave", "Sweave-test-1.Rnw", package = "utils") Sweave(testfile) I then compile Sweave-test-1.tex file using Scientific Workplace 5.5. Apparently, Scienfic Workplace 5.5 does not recognize

Dear list,I have read really a lot the past few days, but I haven't found a matching solution for my problem.I have R 2.9.2 on Windows XP and MikTex 2.8 installed.What I want to do is to automate the sweave file generation.I thought I could use the R2Sweave, RweaveLatex, and Sweave in a combination so thatI won't need to do anything.Perhaps some minor modifications at the last step.My purpose is to print text (summaries) and plots on the same pdf file, fast and easily.If later I need to produce a much more elegant paper I know I will need to fix the latexpart...

I am trying to improve the error reporting in Sweave documents, so that if you have a syntax error in a code chunk, it will tell you which line of your input file contained the error. For example, currently you get this: Error: chunk 1 (label=named) Error in parse(text = chunk) : unexpected symbol in "x <- foo bar" Execution halted and I'd like errors to be more like this:

...dev.off() @ % and then, include it as a picture \includegraphics{figs/myPic.png} ### end of the example ### I This is quite long, and I would have prefered to need simply: <<fig=TRUE,pdf=FALSE,png=TRUE>> ...[code to produce the figure] @ So I tried to adapte the Sweave driver 'RweaveLatex' in order to do so. It worked. The not-so-new driver is only a slight modification of RweaveLatex, and can generate ps, pdf or png figures; it was tested on Ubuntu64, Debian, several Windows systems and macOS X partforms with no detected problem. Does someone find this useful, and/or were t...

Hi, Could R-Core consider adding 'RtangleRuncode' and 'RtangleFinish' to the exports of utils. Their weave equivalent 'makeRweaveLatexCodeRunner' and ?'RweaveLatexFinish' are exported, as well as the other tangle utility functions 'RtangleSetup' and 'RtangleWritedoc'. The rationale is not just symmetry. ;-) I'm finishing a small package that will provide "enhanced" drivers for Sweave th...

Dear R devel, being constrained to a windows environment at work and having colleagues being accustomed to the Microsoft Office Suite, I was looking for a way to have the RweaveLatex driver for Sweave automatically generating 'win.metafile's in addition to the pdf graphics. Without this functionalilty, the generation of emf-graphics is quite laborious, I think: <<>>= plotit <- function () { # code which generates the graphic } win.metafile("fooba...

When using Sweave in connection with the driver RweaveLatex(), global options can be set with \SweaveOpts{}, e.g. \SweaveOpts{keep.source=T}. Does anybody know if it is possible to set global options in the same way when using Sweave with the driver RweaveHTML(). Regards Søren [[alternative HTML version deleted]]

...vice. Hidden, again <<fig =FALSE,echo=FALSE>>= dev.off() @ % and then, include it as a picture \includegraphics{figs/myPic.png} ### end of the example ### I found that quite heavy, though, when more than one such figure were needed in my document. So I adapted the Sweave driver 'RweaveLatex' in order to allow to generate png pictures instead of ps or pdf, when using a pdf-oriented compiler (such as pdflatex). I just have to source the new driver (RweaveInPng), then call it when Sweaving. Then for example, I simply use: ### rnw document ### % a single chunck containing R code...

...s there any way to go from a .Rout file straight to pdf with an Rnw template ? What I'm trying to avoid is adding the Sweave markup to the .tex file manually. What I think I'm missing is the exact arguments to the Sweave command. I tried numerous forms of: Sweave("batch.Rout", RweaveLatex(), "myR.Rnw"); but without any succuess.

In trying to change the driver used by Sweave on the command line using R CMD Sweave --driver=foo I consistently get the "directory 'foo' does not exist' error. (For any value of 'foo', even the default 'RweaveLatex'.) Looking up the source code for function .Sweave that is called by 'R CMD Sweave', I notice that the argument 'driver', if used, is added to the vector of arguments of ''buildVignette' without being named. It ends up being passed to argument 'dir', hence r...

...hods checkTnF checkVignettes codoc md5sum pkgVignettes print.checkAssignFuns print.checkDemoIndex print.checkDocArgs print.checkDocStyle print.checkFF print.checkMethods print.checkTnF print.checkVignetteIndex print.checkVignettes print.codoc print.undoc Rdindex Rtangle RtangleSetup RtangleWritedoc RweaveLatex RweaveLatexOptions RweaveLatexSetup Stangle Sweave SweaveSyntaxLatex SweaveSyntaxNoweb SweaveSyntConv undoc > search() [1] ".GlobalEnv" "package:Tools" "package:tools" "package:methods" "package:ctest" [6] "package:mva"...

...if( length(line) ){ + txt <- sub( "^.*\\SweaveDriver[{](.*)[}]", "\\1", line[1L] ) + driver <- try( eval( parse( text = txt ) ), silent = TRUE ) + if( !inherits( driver, "try-error") ) driver + } +} + Sweave <- function(file, driver=RweaveLatex(), syntax=getOption("SweaveSyntax"), ...) { @@ -28,7 +38,9 @@ else if(is.function(driver)) driver <- driver() - + drv <- SweaveGetDriver(file) + if( !is.null(drv) ) driver <- drv + if(is.null(syntax)) syntax <- Swea...

...and as part of parallel) because the parent and all the children share a session temporary directory, and they can share the C random number stream used to produce the uniaue part. Further, two children can call tempfile() simultaneously. o Option print in Sweave's RweaveLatex() driver now emulates auto-printing rather than printing (which can differ for an S4 object by calling show() rather than print()). o filled.contour() now accepts infinite values: previously it might have generated invalid graphics files (e.g. containing NaN values)....

...and as part of parallel) because the parent and all the children share a session temporary directory, and they can share the C random number stream used to produce the uniaue part. Further, two children can call tempfile() simultaneously. o Option print in Sweave's RweaveLatex() driver now emulates auto-printing rather than printing (which can differ for an S4 object by calling show() rather than print()). o filled.contour() now accepts infinite values: previously it might have generated invalid graphics files (e.g. containing NaN values)....

I have had some fun in the last few days trying to put together an annotated map of China with R and some public GIS data: http://sourceforge.net/projects/outmodedbonsai/files/snpMatrix%20next/1.17.7.11/China_Choropleth_Maps.pdf/download It is done, and rather nice... there are a few issues: - the default pdf() device cannot do CJK with embedded fonts - and cairo_pdf() is not hooked up to

R users, I'm at a loss with a problem considering running .tex files produced by Sweave. When I run (R 2.7.0): --------------------------------------------------- #Taken from ?Sweave testfile <- system.file("Sweave", "Sweave-test-1.Rnw", package = "utils") ## enforce par(ask=FALSE) options(device.ask.default=FALSE) ## create a LaTeX file Sweave(testfile)

...alternative. >> (2) I could enter the code (and the results) in a verbatim environment >> instead of using Sweave. This has obvious drawbacks (for one thing, it >> would look incosistent). use the chunk argument eval=FALSE instead of placing the code in a verbatim argument. See ?RweaveLatex if you're compiling a PDF vignette from Rnw or the knitr documentation for (much nicer for users of your vignette, in my opinion) Rmd vignettes processed to HTML. A common pattern is to process chunks 1, 2, 3, 4, and then there is a 'leap of faith' in chunk 5 (with eval=FALSE) and a...

Hello List, I have been using Sweave for my homework this last quarter and have been very impressed at how much time and effort it saves me. I, however, have run up against a problem which I have not been able to solve using any of the Sweave/LaTeX tricks I know. I work through my homework one problem at a time, typesetting equations and writing R code, etc. and occasionally use

When loading mclust, it shows a license agreement message. This message shows up in my document when I use Sweave. I did the following: <<echo=FALSE,include=FALSE>>= library(mclust) @ Is this a problem with mclust, Sweave or with me? How can it be fixed? Thanks for any suggestions! Titus