similar to: How to include a vignette with my package?

Displaying 20 results from an estimated 500 matches similar to: "How to include a vignette with my package?"

2003 Oct 23
1
texi2dvi and buildVignettes() on Windows
I am currently writing a (private) package in which I produce pdf files from within R using LaTeX. To do so I mainly copied some lines from the buildVignettes() function in the tools package. This uses the texi2dvi which is included in R's bin directory: system(paste(file.path(R.home(), "bin", "texi2dvi"), "--quiet --pdf", bft)) This runs
2008 May 04
1
texi2dvi instead of pdflatex in R2.7.0? and related bioc 2.2 builds
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 =
2008 Jun 02
2
How can I solve this function in R?
I would like to solve the following function in R: G <- function(k) (2*(1 - k)*(1 + 2*k)^.5)/(1+3*k) I want to be able to find "k" for a given "G" Thanks! Francois Aucoin [[alternative HTML version deleted]]
2008 Jul 19
2
How to solve systems of nonlinear equations in R?
Hey, I was wondering if there existed a R function similar to 'fsolve' or 'fzero' Matlab functions? Thanks! Francois Aucoin [[alternative HTML version deleted]]
2013 Sep 15
1
FOSS licence with BuildVignettes: false
Dear All, I have been checking the metafor package against R-devel. R CMD check --as-cran metafor yields one note: FOSS licence with BuildVignettes: false Yes, I have 'BuildVignettes: FALSE' in my DESCRIPTION file. I see at http://developer.r-project.org/blosxom.cgi/R-devel/NEWS: Tue, 25 Jun 2013 CHANGES IN R-devel UTILITIES 'R CMD check --as-cran' warns about a false
2012 Mar 28
2
--as-cran / BuildVignettes: false
I have packages where I know CRAN and other test platforms do not have all the resources to build the vignettes, for example, access to databases. Previously I think putting BuildVignettes: false in the DESCRIPTION file resolved this, by preventing CRAN checks from attempting to run the vignette code. (If it was not this, then there was some other magic I don't understand.) Now, when
2008 Jun 04
1
Minimizing the negative log likelihood function...
Hey, The following is a function I wrote which generates random variables from a Kappa (2-parameter) distribution. rkappa <- function(n,beta,alpha){ if(alpha <= 0) stop("alpha must be greater than zero!") if(beta <= 0) stop("beta must be greater than zero!") Vec <- beta*exp((1/alpha)*(log(-(alpha/(-1 + exp(alpha*log(runif(n,0,1))))))+
2013 Mar 03
1
Missing PROTECT in mkPRIMSXP ?
The Bioconductor build for a package DirichletMultinomial on R Under development (unstable) (2013-02-26 r62077) -- "Unsuffered Consequences" at http://bioconductor.org/checkResults/devel/bioc-LATEST/DirichletMultinomial/george2-buildsrc.html shows * creating vignettes ... ERROR ... Error: processing vignette ?DirichletMultinomial.Rnw? failed with diagnostics: chunk 21 (label
2013 Aug 28
1
Error when using buildVignettes()
Dear all, When running function 'testQAReport()', which uses function 'buildVignettes()' to create a pdf-file I get the following error: > source("testQAReport.R") > testQAReport() Error in .get_package_metadata(pkgdir) : Files 'DESCRIPTION' and 'DESCRIPTION.in' are missing. Since I did not get this error in earlier versions of R, could you
2005 Mar 22
1
Package vignette and build
Hello, I am writing a package called 'DLM' containing a vignette. The vignette contains a chunck with the function call 'library(DLM)'. This worked fine with 'R CMD check DLM', but when it comes to building the package with 'R CMD build DLM' I get the following error message: * creating vignettes ... ERROR Error: chunk 1 Error in library(DLM) : There is no
2012 May 14
1
Vignette problem
I'm having a problem rebuilding a package, new to me in R 2.15.0 (Linux) It hits all that contain the line \usepackage[pdftex]{graphics} and leads to the following when running R CMD check on the directory. (I do this often; a final run on the tar.gz file will happen before submission.) Since I float and resize my figures, removing the line is fatal in other ways.
2017 Dec 06
2
FW: R-devel error
Interesting, yesterday I had exactly this problem, but today I solved it (see the R-pkg-devel list) by _installing_ R-devel and > update.packages(checkBuilt = TRUE) I also tried it on Martin's Fedora 26 example below. Worked fine (had to install some packages...) On ubuntu 16.04. G?ran Brostr?m On 2017-12-06 11:29, Martin Maechler wrote: >>>>>> Pearce, Robert
2010 Sep 16
1
Lack of consistent cross-platform behaviour of tools:::buildVignettes()
Hi, On both Unix and Windows there is a mechanism to add variables to the environment when R is started. I noticed that, on Unix, this mechanism is not used when R is started normally at the command line but only when it's started using the 'R CMD' syntax. One problem with this is some lack of consistent cross-platform behaviour. For example: On Linux: $ echo $TEXINPUTS $
2014 Apr 05
1
Package vignettes share the same environment?
In a package 'vig' R CMD build vig (or tools::buildVignettes(dir="vig") with $ cat vig/vignettes/vig1.Rnw \documentclass{article} \begin{document} <<>>= x <- 1 @ \end{document} $ cat vig/vignettes/vig2.Rnw \documentclass{article} \begin{document} <<>>= x @ \end{document} produces vig2.pdf where x is defined with value 1 -- the vignettes share a build
2009 May 17
3
build CONTENTS or 00Index.html without installing whole package
To maintain my R site, I'm trying to install html help files only, but also keep track of the version (with DESCRIPTION). I have the following bash script, which works except for 00Index.html. That is not a huge problem because the help files are still searchable, but I'd like to fix it. A long time ago I asked the same question, and Brian Ripley said to use --index as an option to
2017 Jun 27
2
texi2pdf doesn't find the correct MikTex installation due to erroneous Sys.which()
I checked after this question popped up on Stackoverflow: https://stackoverflow.com/questions/44785961/compile-pdf-in-rstudio-works-but-knit2pdf-does-not-work-in-r-or-rstudio On Windows, texi2pdf looks for the texify.exe of Miktex, but looks in a very wrong place: > Sys.which("texify") texify
2010 Sep 15
1
running 'make' failed during vignette creation ('R CMD build') on Windows
Hi, This is a follow-up to the problem reported here: https://stat.ethz.ch/pipermail/r-devel/2010-September/058460.html After I updated R-2.12 to 2010-09-13 r52905 on the Bioc build system, some of the packages that have a Makefile in <pkg>/inst/doc still don't build on Windows. For example, 'R\bin\R.exe CMD build adSplit' gives: * checking for file
2004 Dec 29
3
Windows vignettes, shQuote, texi2dvi
I noticed a shQuote fix for Windows in the svn logs. Just wanted to point out that this will favorably affect texi2dvi on Windows which previously used UNIX quoting and so generated an incorrect Windows command. (Note that texi2dvi is used when creating vignettes.) Another problem is that the recommended tex distribution for Windows, fptex, does not have texi2dvi in the first place. The
2005 Jan 19
1
* creating vignettes ... ERROR
Hi, I have the following error when building a package * creating vignettes ... ERROR Error: chunk 3 Error in pmatch(x, table, duplicates.ok) : argument is not of mode character Error in buildVignettes(dir = ".") : Error: chunk 3 Error in pmatch(x, table, duplicates.ok) : argument is not of mode character Execution halted I use R-2.0.1 under debian linux 2.6.9
2005 Jan 21
2
* creating vignettes ... ERROR
Dear R developers, I had some problem when building package: for exemple when building the package e1071 available from CRAN, I get the following message error: * checking for file 'e1071/DESCRIPTION' ... OK * preparing 'e1071': * cleaning src * running cleanup * creating vignettes ... ERROR /usr/lib/R/bin/texi2dvi: pdflatex exited with bad status, quitting.