similar to: Cran package checks

Displaying 20 results from an estimated 10000 matches similar to: "Cran package checks"

2013 Aug 23
2
packages with Sweave and knitr vignettes?
Now that R 3.0.0+ supports non-Sweave vignettes, R-exts \S 1.4.2 seems to imply that it is possible to include both Sweave and knitr vignettes in a single package. I'm wondering if anyone has tried this and/or if there are some hidden gotchas putting this into practice, and concerned about creating problems with CRAN checks if I try this. Consider two vignettes: pkg/vignettes/vign1.Rnw,
2013 Sep 17
2
processing of /vignettes and /inst/doc
It is stated in R-exts that Sweave files (.Rnw) are either processed in /vignettes or /inst/doc, not both. Furthermore, it is stated that external manuals and other files in /inst/doc will be installed. This behaviour has been used to deal with the situation where a package has two "vignettes", one that is easily processed and one that has a long running time. This could be done by
2012 Apr 11
2
Vignette questions
Context: R2.15-0 on Ubuntu. 1. I get a WARNING from CMD check for "Package vignette(s) without corresponding PDF: In this case the vignettes directory had both the pdf and Rnw; do I need to move the pdf to inst/doc? I'm reluctant to add the pdf to the svn source on Rforge, per the usual rule that a code management system should not have both a primary source and a object
2011 Nov 07
3
CRAN: How to list a non-Sweave doc under "Vignettes:" on package page?
Hi, is it possible to have non-Sweave vignettes(*) in inst/doc/ be listed under 'Downloads' on CRAN package pages? For instance, in my R.rsp package I have a inst/doc/report.pdf (part of the source *.tar.gz) that is not detected/listed. The PDF is not based on a Sweave vignette but an *.tex.rsp vignette that is dynamically created via inst/doc/Makefile. It is listed (*) BTW, can the
2013 Jan 22
1
file.system() in packages
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
2015 Mar 25
2
vignette checking woes
I'm having trouble with R CMD check of my quantreg package. All is well until I get to: checking running R code from vignettes ... ?rq.Rnw? ... failed ERROR Errors in running code in vignettes: when running code in ?rq.Rnw? when I see a snippet from the vignette code and then: Loading required namespace: MatrixModels When sourcing ?rq.R?: Error: could not find function
2013 Feb 11
1
Avoid re-building a vignette
I once knew the answer to this, but can't find where I found it. Say I have a vignette that I don't want R to automatically rebuild, perhaps it uses some data I can't share or takes too long to run or whatever. Say it is mypackage/vignettes/charlie.Rnw It can create the pdf from an R session that actually has the data, place that result in inst/doc/charlie.pdf, then run R
2012 Jun 06
1
stumped on re-building package vignette
[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
2024 Mar 11
2
Vignettes with long compute time
Is there a way to include the compiled version of a vignette in the doc directory but mark it to NOT be rerun by CRAN??? I think I remember that this is possible, but have forgotton how.?? (It might even be a false memory.) Terry T. Background:? Beth Atkinson and I are splitting out many of the vignettes from the survival package into a separate package survivalVignettes.? There are a few
2013 Oct 22
1
possible Sweave problem in rdevel build on Debian 6.0.8?
Dear R-sig-debian, As of last night, we are running into a build failure when trying to compile the development version of R from the svn repository, Revision: 64090: ./configure && make -j4 distclean && ./configure && make -j4 [lots of normal compile output not shown...] building/updating vignettes for package 'utils' ... processing 'Sweave.Rnw' Error:
2004 Oct 29
3
R-exts.texi: suggestion for small change to Vignette section (PR#7323)
I recently wrote a vignette, with the following at the top of the .Rnw file: %%\VignetteIndexEntry{How to use look up tables for h() functions} %%\VignetteDepends{sjedmin, spatstat} Using vExplorer() on this function, I got an error from this part of getVigInfo(): lines <- grep("^%[[:space:]]*\\\\Vignette", file) if (length(lines) == 0) stop("File ", vig,
2013 Oct 22
1
possible Sweave problem in rdevel build on Debian 6.0.8?
Dear R-Devel, Note: I posted a similar message to R-sig-debian yesterday because I assumed it was a Debian issue, received response that it it may be more appropriate for r-devel since it involves building from the svn version. As of Oct 21, we are running into a build failure when trying to compile the development version of R from the svn repository. The problem still persists as of
2015 May 16
2
That 'make check-all' problem with the survival package
------------------------------ On Sat, May 16, 2015 8:04 AM BST Uwe Ligges wrote: >Not sure why this goes to R-devel. You just could have asked the >maintainer. Terry Therneau is aware of it and promised he will fix it. > The quickest fix is to add cmprsk to the recommended list , and that's is an R-devel issue. >On 16.05.2015 07:22, Hin-Tak Leung wrote: >> 'make
2013 Feb 15
1
Suggestion: Custom filename patterns for non-Sweave vignettes
Hi, as far as I understand it, the new R devel feature of processing non-Sweave vignettes will (a) locate any "[.][RrSs](nw|tex)$" or ".Rmd" files, (b) check for a registered vignette engine, (c) process the file using the registered "weave" function, (d) and possibly post process the generated weave artifact (e.g. a *.tex file). I'd like to propose to extend
2009 May 10
2
Vignettes with missing or empty \VignetteIndexEntry:
Hi, I have a problem when checking the package 'probdistr' (on probability distributions). I got this warning * checking index information ... WARNING Vignettes with missing or empty \VignetteIndexEntry: [1] "probdistr-chi" "probdistr-contextra" "probdistr-discrete" [4] "probdistr-discrextra" "probdistr-exp"
2011 Mar 30
1
R CMD build processes inst/doc/Makefile only if there are vignette files?
Hi, in Section 'Writing package vignettes' of 'Writing R Extensions' it says: "Whenever a Makefile is found, then R CMD build will try to run make after the Sweave runs, so PDF manuals can be created from arbitrary source formats (plain LaTeX files, ...). [...] Note that the make step is executed even if there are no files in Sweave format, [...]". In my package,
2014 Aug 25
1
vignette index going AWOL
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
2010 Aug 19
5
Does anyone use Sweave (RweaveLatex) option "expand=FALSE"?
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:
2015 Feb 27
2
static pdf vignette
Dear all, In my package I have a computational expensive Rnw file which can't pass R CMD check. Therefore I set eval=FALSE in the Rnw file. But I would like to have the pdf vignette generated by the Rnw file with eval=TRUE. It seems to me a static pdf vignette is an option. Any suggestions on this? Thanks, Zhu Wang **Connecticut Children's Confidentiality Notice** This e-mail
2013 Jul 17
1
SweaveParseOptions, quoted commas, and knitr vignettes
I haven't figured it out entirely, but it looks like there are a couple of small glitches with knitr-based vignettes and SweaveParseOptions. I posted the tarball of a package with a knitr vignette with (as far as I can tell) everything properly coded in the DESCRIPTION file (VignetteBuilder: knitr, Suggests: knitr) and the vignette itself (%\VignetteEngine{knitr::knitr}). When Windows