search for: rmarkdowns

On 5/3/16 11:29 AM, Thierry Onkelinx wrote: > Dear Mick, > > Note that both knitr and rmarkdown are listed under Suggests: both are > required to compile the vignette. Installing rmarkdown should solve > the problem. If not, please provide more information. OS, R version, > digest version, ... > > This is occurring in the context of an automated testing environment that

Dear List, I am working on moving some Rmarkdown reports into the vignettes folder of a package. While I was able to solve to problem of parametrized reports in vignettes folder thanks to your invaluable help (Thank you), I am now struggling with the following problem. One of the reports which I am moving to vignettes includes the following code : ```{r} child_docs <-

Dear Duncan, Thanks for chiming in. Could you explain how you set debug() on post_processor()? I've tried adding debug(post_processor) to rsos_article() or adding debug(post_processor) when after post_processor was defined in the debugger. Neither work for me. All supporting files are available within the package. The code below should be reproducible on your machine.

On 07/09/2017 2:04 PM, Duncan Murdoch wrote: > On 07/09/2017 10:11 AM, Thierry Onkelinx wrote: >> Dear Duncan, >> >> Thanks for chiming in. Could you explain how you set debug() on >> post_processor()? I've tried adding debug(post_processor) to >> rsos_article() or adding debug(post_processor) when after post_processor >> was defined in the debugger.

I need some help understanding a problem running the tests on the 'digest' package. Initially, I got the message that the 'knitr' package was needed to run vignettes: Running vignettes for package ?digest? Error in loadVignetteBuilder(vigns$pkgdir) : vignette builder 'knitr' not found So I installed the knitr package and all its dependents (?mime?, ?stringi?,

That is strange. Another function in the same package (INBOmd::inbo_rapport) uses the same trick. I actually started by copying the post_processor() from that function. INBOmd::inbo_rapport() works both with and without BibTex. Working examples are source/inbo_rapport and source/inbo_rapport_basic from https://github.com/inbo/inbomd_examples. Note that you need some extra work after installing

On 07/09/2017 10:11 AM, Thierry Onkelinx wrote: > Dear Duncan, > > Thanks for chiming in. Could you explain how you set debug() on > post_processor()? I've tried adding debug(post_processor) to > rsos_article() or adding debug(post_processor) when after post_processor > was defined in the debugger. Neither work for me. Not working for me either right now for some reason

On 06/09/2017 5:41 AM, Thierry Onkelinx wrote: > Dear all, > > I'm trying to write a post_processor() for a custom rmarkdown format. The > goal of the post_processor() is to modify the latex file before it is > compiled. For some reason the post_processor() is not run. The > post_processor() does work when I run it manually on the tex file. > > Any suggestions on what

Buenas noches: Estoy realizando un documento rmarkdown donde realiza un modelo de random forest con la librería H2O, el problema lo tengo cuando lo compilo con knit a pdf, ya que en el documento me sale con rayas con el porcentaje de entrenamiento que lleva. ¿Alguien sabe como eliminarlas para que no aparezca en el documento en pdf? [cid:image001.png en 01D49FC5.4D2AEEE0] Muchas Gracias. Un

Buenas noches, Escribo este mail porque tengo un problema con rmarkdown, estoy creando un informe y me iba bien al generarlo como pdf, de repente me sale el siguiente error y no sé como solucionarlo: pandoc.exe: Error producing PDF from TeX sourceError: pandoc document conversion failed with error 43Además: Warning message:comando ejecutado '"C:/Program

Buenas tardes, Al tratar de hacer en rstudio documentos pdf, word o html con un archivo rmd me sale un mensaje tal que así: "Rendering R Markdown documents requires updated versions of the following packages: knitr, rmarkdown. Do you want to install these packages now?" He probado a reinstalar esos paquetes (que ya tenía instalados) pero cuando vuelvo a aplicar knit to pdf,

On 10/07/2018 11:44 AM, Witold E Wolski wrote: > Dear List, > > I am working on moving some Rmarkdown reports into the vignettes > folder of a package. While I was able to solve to problem of > parametrized reports in vignettes folder thanks to your invaluable > help (Thank you), I am now struggling with the following problem. > > > One of the reports which I am

Hello, This is a problem I posted about already some time ago: https://stat.ethz.ch/pipermail/r-devel/2018-September/076786.html Finally, I did had some time to create a minimal package to reproduce the problem that vignettes with child can not be build. https://github.com/wolski/RmarkdownVignetteProblem The problem basically is that while all the vignettes can be build by running

Dear all, I'm trying to write a post_processor() for a custom rmarkdown format. The goal of the post_processor() is to modify the latex file before it is compiled. For some reason the post_processor() is not run. The post_processor() does work when I run it manually on the tex file. Any suggestions on what I'm doing wrong? Below is the relevant snippet of the code. The full code is

Dear Duncan, Thank you, got it working with your advice. I did placed the child markdown documents into inst/ParametrizedReportsChild And this is the code in the main vignette by which I include them: child_docs <- "Grp2Analysis_MissingInOneCondtion.Rmd_t" if(!sum(NAinfo$nrProteins > 0) > 0){ child_docs <- "Grp2Analysis_Empty.Rmd_t" } child_docs <-

A few things to clarify: 1. You do not necessarily have to keep the \usepackage{} line if you use %\VignetteEncoding{UTF-8}, because Pandoc will use UTF-8 anyway in its LaTeX template. 2. Perhaps the vignette engine in R has done something clever to convert utf8 to UTF-8, but I'd recommend %\VignetteEncoding{UTF-8} instead of %\VignetteEncoding{utf8} to make sure it is a valid encoding name,

Suppose I have a file (named "tmp.rmd") containing: --- title: Test --- ```{r example, echo=FALSE, results='asis'} tmp <- data.frame(a=1:5, b=letters[1:5]) print( knitr::kable(tmp, row.names=FALSE)) ``` And I render it with: rmarkdown::render('tmp.rmd', output_format=c('html_document','pdf_document')) I get two files: tmp.pdf tmp.html Is

Hi Dan, Hi All, I read the below post. I am wondering how do I know which "keys" are available, e.g. "core.r" and "pre". Where kind I find the definition of what can be adjusted and which "words" to use? Kind regards Georg > Gesendet: Donnerstag, 08. Juni 2017 um 16:16 Uhr > Von: "Nordlund, Dan (DSHS/RDA)" <NordlDJ at

Hola, colegas, compañeros y maestros. Es una tontería... que no atino a preguntarsela bien a Google. Tengo unos datos a los que si en consola les digo: > sum(dtk$V9) [1] 37790 devuelve. Pero si eso mismo se lo digo en RMarkdown con código on line, lease `r sum(dtk$V9)` me devuelve un numero horroroso: 3.77910^{4} entre el texto Qué, para colmo, ocupa más carácteres que el que no me imprime.

Hola, cuando ejecuto Rmarkdown los gráficos plotly no salen. No hay ningún error pero en el resultado final no se obtiene nada. Si ejecuto plotly desde R los gráficos primero salen en blanco y es necesario "recargar" para poderlo ver, si lo inspeccionas no sale nada. El equipo en el que me pasa esto es: platform x86_64-w64-mingw32 arch x86_64 os mingw32