similar to: Building packages

Writing R extensions says: In addition to the help files in Rd format, R packages allow the inclusion of documents in arbitrary other formats. The standard location for these is subdirectory inst/doc of a source package, the contents will be copied to subdirectory doc when the package is installed. Pointers from package help indices to the installed documents are automatically created.

Dear colleagues, I am having issues trying to build a R package I recently wrote. I am using R 2.14.0 and my package depends on another package called aod. Running: R CMD Sweave vignette.Rnw is perfectly fine and the vignette compiles properly. but when I use R CMD build mypackage to build the tar.gz I get the following error: * installing the package to re-build vignettes * creating

I don't think anyone denies that you *could* make an EXE to do all that. The discussion is on *how easy* it should be to create a single file that contains an initial "main" function plus a set of bundled code (potentially as a package) and which when run will install its package code (which is contained in itself, its not in a repo), install dependencies, and run the main()

Dear lists: I am somewhat puzzled by the use of texi2dvi/pdflatex in R2.7.0. When building EBImage (bioconductor) with 2.7.0 I get the same error both in Windows and Linux, which reads the following: ** building package indices ... * DONE (EBImage) * creating vignettes ... ERROR /usr/bin/texi2dvi: pdflatex exited with bad status, quitting. Error in texi2dvi(file = bft, pdf = TRUE, clean =

Is there any interest in a method of taking a package with documentation in Rd files and attaching it to package R files in Roxygen format? I can see a few problems with a totally general solution but it might be possible to make a script that provides a kickstart to converting a package to Roxygen. Or is it trickier than it seems? Barry

Hello, The vignette concept, which started in Bioconductor, seems to be catching on. They are supported by R CMD build/check and documented in the Writing R Extensions manual. I think vignettes are a fantastic way to introduce new users to a package. However, getting new users to realize that a vignette is available can be challenging. For some time now, we have had a function in Biobase that

On Mon, Feb 29, 2016 at 6:17 PM, John Chambers <jmc at r-project.org> wrote: > The Wikipedia statement may be a bit misleading. > > S was never open source. Source versions would only have been available with a nondisclosure agreement, and relatively few copies would have been distributed in source. There was a small but valuable "beta test" network, mainly university

[Env: Win Xp / StatET 2.0 / R 2.15.0] In my heplots package I extended the HE-examples.Rnw vignette under inst/doc. The package passes R CMD check on my machine: * using log directory 'C:/eclipse-3.7/heplots.Rcheck' * using R version 2.15.0 (2012-03-30) * using platform: i386-pc-mingw32 (32-bit) ... * checking sizes of PDF files under 'inst/doc' ... OK * checking installed files

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

I see some value in Duncan?s proposal to implement this as an extra package instead of a change to base R, if only to see if the idea has legs. I?m minded to do so myself using your suggestion, but is there a particular reason why you recommend using the remotes package instead of devtools? The latter seems to have the same functions I would need, and I believe it is more widely installed 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 <-

A colleague is receiving some data from another person. That person reads the data in SAS and it takes 30s and uses 64k RAM. That person then tries to read the data in R and it takes 10 minutes and uses a gigabyte of RAM. Person then goes on to say: It's not that I think SAS is such great software, it's not. But I really hate badly designed software. R is designed by

I wondered if there were standard practices in CRAN for delivery of R source implementing functions in R packages. I has encountered a couple of packages where the gzipped version of source contains very little, primarily the Help files describing the functions in the package. In some cases I can find the source as the value of the function name. Given that these packages are released as GPL,

Dear R-devel, Question: How can I get Sweave to recognize that the \thebibliography section is already created and generate the vignette pdf with a single pass? Or is there a way to let R CMD build know that Sweave needs to be run twice? If (1) is not possible, any suggestions how to auto-generate a crude generic bibtex .bib file from my existing document? Background: I maintain

Hello. R-devel, r61697. I am having difficulty interpreting section 1.4 "Writing package vignettes" of the R-exts manual. Specifically, I want to use system.file() in some of my packages to locate a bib file, uncertainty.bib, which is part of the emulator package. I only want to maintain a single .bib file. R-exts says: "All other files needed to re-make the vignette PDFs (such

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

On Thu, Jul 26, 2018 at 12:22 AM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > I am trying to control a background R session, connected via a fifo / > named pipe. Is the fifo significant here? If I read the same R code from a file via `<` I get the input echoed (R 3.4.4, Ubuntu). Barry

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

I apologize that these questions are stupid and literal. I write to ask for clarification of comments in the R extensions manual about vignettes. I'm not great at LaTeX, but I'm not a complete novice either, and some of the comments are puzzling to me. 1. I'm stumbling over this line: "Make sure all files needed to run the R code in the vignette (data sets, ...) are accessible

Dear all, I am struggling with an issue related to static vignettes: they work, but only when present in double in the tarball -- in the folder inst/doc and vignettes; see below for details. Details: I am pre-compiling heavy vignettes thanks to the vignette builder R.rsp. So basically, I have PDF files which I want the package to use as Vignettes. For this, I have the following in my