similar to: new package TSrepr

Georges Monette and I would like to announce a new package, cv, now on CRAN, which implements cross-validation of regression models. Some of the functions supplied by the package: - cv() is a generic function with a default method and computationally efficient "lm" and "glm" methods, along with a method for a list of competing models. There are also experimental

Georges Monette and I would like to announce a new package, cv, now on CRAN, which implements cross-validation of regression models. Some of the functions supplied by the package: - cv() is a generic function with a default method and computationally efficient "lm" and "glm" methods, along with a method for a list of competing models. There are also experimental

You are doing a lot of things that are non-standard, so I doubt if anyone is going to be able to help you without access to a simple reproducible example of a package that does what you do. Try to cut out as much as you can to make it minimal. For example, devtools::document() (indeed, most of your code) is probably irrelevant to your problem with vignettes, but things like your

Noted Duncan and TRUE... I cannot do more immediately unfortunately, that is always the issue of asking a last minute panic attack question before teaching a course involving the package... I do have /doc in my .Rbuildignore for reasons I can no longer remember... I will dig and create a MRE/reprex. The students will download heavy packages, but they probably won't notice. *Apologies* In the

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

On Thu, Sep 20, 2018 at 11:46 AM Leo Lahti <leo.lahti at iki.fi> wrote: > > Time stamps are correct and my system time is correct. > > I am now tried to use Sys.setFileTime() to update time stamps as proposed. > This does not help. > > The windows and debian builds give different reports on the time stamp > issue. >

From: Duncan Murdoch <murdoch.duncan at gmail.com> To: Mark van der Loo <mark.vanderloo at gmail.com> Cc: Dirk Eddelbuettel <edd at debian.org>, r-devel <r-devel at r-project.org> Further to Duncan's comments: > It would be nice if the documents in inst/doc were linked to on the CRAN > landing page of a package. I think that documents under inst/doc are a

I'l like to chime in on the subject of vignette checks. I have one vignette in the coxme library that would be better described as a white paper. It discusses the adequacy of the Laplace transform under various scenarios. It contains some substantial computations, so I'd like to mark it as "never ever run this" for both CRAN and my local builds, my next update of it will

I?m preparing a package (fastR) for submission to CRAN, but the vignette index keeps going AWOL, or at least R CMD check ?as-cran thinks so. I?ve tried several things and gave myself the weekend to think of other things, but I can?t figure it out. Perhaps someone on the list can lend a hand. Here?s one example situation, where I build the index.html file myself and put it in inst/doc/index.html

In R 3.1.0 (~April 2014), support for vignettes in inst/doc/ will go away (and probably much sooner for CRAN submission), e.g. checking for old-style vignette sources ... NOTE Vignette sources only in ?inst/doc?: ?R.devices-overview.tex.rsp? A ?vignettes? directory is required as from R 3.1.0 and these will not be indexed nor checked I've been sticking with inst/doc/ for backward compatible

Hi folks, For ubuntu specs and for a better desktop integration of compiz, I made some patchs and plugins. Focus prevention is now in main stream, and really better can i made :) First the workspace and terminal keybinding patch. Since my last email I updated the patch. http://gandalfn.club.fr/ubuntu/compiz-patch/91-workspaces-terminal-keybindings.patch It adds the support for vertical

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

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

OK, I see now that I was supposed to twig that the reference was to putting the ?.Rnw' files back into the vignettes directory from the inst/doc directory where they?d been placed in the course of creating the tar.gz file. I am still trying to work out what I need to put into ?.Rinstignore? so that ?.install_extras? is not installed. John Maindonald email: john.maindonald at

I am experimenting with putting vignettes in a vignettes/ directory as suggested in the new R release news. If I understand correctly, it is now suggested that the vignette source (.Stex in my case) should be in the vignettes/ directory and the pdf should be put in the inst/doc/ directory, for the case when it is not being built by R CMD build. I am getting an error (R-2.14.0): (cd inst/doc ;

On 19/02/2018 5:47 AM, Michael Hannon wrote: > Thanks, Duncan. The files in question are Emacs Org-mode files, and I > think these are more or less isomorphic to Rmd files, but I haven't > used Org-mode in a long time, so I think the mapping (Org-mode ==> > Rmd) would be painful. If they aren't LaTeX then they won't be able to masquerade as Sweave files, so things are

On 09/12/2014 11:13 AM, Yihui Xie wrote: > 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

On Sun, Nov 1, 2020 at 10:39 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 01/11/2020 2:57 p.m., Dirk Eddelbuettel wrote: > > > > The closest to a canonical reference for a static vignette is the basic > blog > > post by Mark at > > > > > https://www.markvanderloo.eu/yaRb/2019/01/11/add-a-static-pdf-vignette-to-an-r-package/ > >

On 18/02/2018 9:06 PM, Michael Hannon wrote: > Greetings. The group that I work with has just started using the approach > outlined in Karl Broman's handy primer: > > http://kbroman.org/pkg_primer/pages/vignettes.html > > to create vignettes for a couple of R packages. > > This works fine as long as we have a current Rmd version of the vignette. But > we