similar to: RMarkdown Vignettest in R packages with child is failing in package build

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

Dear Community, I have an Rmarkdown vignette with optional child documents. Since all markdown files in the vingette folder are build when executing R CMD build I did place the child documents in /inst/ParametrizedReportChid/ so they are excluded from the build. I do reference them from the markdown file in the vignette folder by: ```{r referencingChildDocument} child_docs <-

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 Duncan, Following your advice (Thank you for it) I did include into the vignettes params: configuration: !r get(data(sample_analysis)) data: !r get(data(skylineconfig)) And everything seemed (see below) to work fine. devtools::build_vignettes() builds the vignettes. Runs with NO error. By this the .Rmd file, html file and corresponding .R files is being placed into the inst/doc

Hello, Thank you for the questions as well as remaining me of the default parameters in the yaml session. Indeed this seems to be the solution. But how would I assign package data as a default parameter? So originally I thought to render the markdown with : <code> data(sample_analysis) data(skylineconfig) x <- rmarkdown::render("report.Rmd", output_format =

So far you haven't provided a reproducible example yet. I wonder what exactly the object `sample_analysis` is. Sounds like it is an environment. If that is the case, devtools::build_vignettes() will tangle (for the meaning of "tangle", see ?tools::buildVignette) your vignette into an invalid R script. Environments cannot be represented via dput(), so knitr's purl() (eventually

On 09/07/2018 8:49 AM, Witold E Wolski wrote: > Dear Duncan, > > Following your advice (Thank you for it) I did include into the vignettes > params: > configuration: !r get(data(sample_analysis)) > data: !r get(data(skylineconfig)) > > And everything seemed (see below) to work fine. > devtools::build_vignettes() builds the vignettes. > > Runs with NO

Dear Yihui, Thank you for the valuable questions. sample_analysis is a "tibble" while configuration is an "R6" class. But I also have parametrized reports where I pass R reference classes as arguments. This is the Rmd yaml params part corresponding to the error message. params: configuration: !r get(data(skylineconfig)) data: !r get(data(sample_analysis)) Might the R6

On 02/07/2018 10:30 AM, Witold E Wolski wrote: > Hello, > > I have a package which includes some parameterized r-markdown report > which I would also like to build as package vignettes. > > Is there a way to run the parameterized vignette creation with the > package build or package check? Doesn't the usual method work? You can specify defaults for parameters in the

On 02/07/2018 11:22 AM, Witold E Wolski wrote: > Hello, > > Thank you for the questions as well as remaining me of the default > parameters in the yaml session. > Indeed this seems to be the solution. > > > But how would I assign package data as a default parameter? > So originally I thought to render the markdown with : > > <code> >

Dear Duncan, Was close to giving up to use the parameterized rmarkown as vignettes. But your suggestions to use quote and eval, as well as to use the package parameter in data made it work, with all devtools::install,check,build and build_vignettes as well as with R CMD ... etc. But most importantly it also still works with: rmarkdown::render("vignettes/tr_srm_summary.Rmd",

Hello, I have a package which includes some parameterized r-markdown report which I would also like to build as package vignettes. Is there a way to run the parameterized vignette creation with the package build or package check? Thank you -- Witold Eryk Wolski

On 09/07/2018 3:24 PM, Witold E Wolski wrote: > Dear Yihui, > > Thank you for the valuable questions. > > sample_analysis is a "tibble" while > configuration is an "R6" class. > But I also have parametrized reports where I pass R reference classes > as arguments. > > This is the Rmd yaml params part corresponding to the error message. > >

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

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

Although it is not an elegant solution, but if your output format is HTML, you can add an arbitrary empty HTML element like <span id="foo"></span> before your code chunk. Then you can jump to this <span> via a link like "see [this code chunk](#foo)". Regards, Yihui -- https://yihui.name On Tue, Aug 29, 2017 at 1:30 PM, Roy Mendelssohn - NOAA Federal

Buenas, he intentado varias veces instalar knitr y Rmarkdown tanto desde Rstudio como desde la terminal de Ubuntu usando diferentes codigos y en nunca consegui q lo instalara. el error q tira es el siguiente: Warning in install.packages : installation of package ?/tmp/RtmpavyTWw/downloaded_packages/stringr_1.0.0.tar.gz? had non-zero exit status Alguien me podria ayudar, porq estoy dejando