similar to: running 'make' failed during vignette creation ('R CMD build') on Windows

Hi everyone, I have trouble to use RWeka, I tried: (w=weather dataset, all preditors are nominal) > m<-J48(play~., data=w) > e<-evaluate_Weka_classifier(m,cost = matrix(c(0,2,1,0), + ncol = 2),numFolds = 10, complexity = TRUE,seed = 123, + class = TRUE) it gives me exactly what I want, but when I tried the same classifier on the other published data: (iris dataset has all numeric

Hi, The following command: R CMD Rd2pdf --no-preview --output=./tmp.pdf --title=test genefu-package.Rd run against this file: https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/genefu/man/genefu-package.Rd (username: readonly; password: readonly) produces a very verbose error (see below) with R version 2.15.0 alpha (2012-03-07 r58622). The .Rd file has these lines in it: Version: \tab

Dear R?ers I?m trying to get a summary table using latex and summary in the rms package to no avail. I?m running R 2.10.1, Mac OS X snow leopard and I have the mactex 2009 distribution installed. Any obvious things I?m missing? //M options(digits=3) set.seed(173) sex <- factor(sample(c("m","f"), 500, rep=TRUE)) age <- rnorm(500, 50, 5) treatment <-

Dear useRs-- I have been using Sweave with miktex for years, but on a new install on Windows XP, miktex seems to be hung up on single quotes. See example below. Digging through stackexchange, I found using \usepackage[noae]{Sweave} in the tex file solved the problem. My questions are: --Why would this happen? I have the ae package installed. --If inserting [noae] is the solution, how do I

In the process of updating R to R 2.7 alpha or R 2.7 beta for the BioConductor 2.2 builds on Windows, I have hit a snag because the BioC build system has long path names (e.g. D:\biocbld\bbs-2.2-bioc\R) and these path names are not resolving properly by MiKTeX 2.7 during vignette construction. Take, for example, the attached vignette from Biobase, Bioconductor.Rnw. I have built R from source

Hi, All: I encountered problems running "pdflatex wrapper.tex", as suggested on "www.r-project.org" -> Newsletter -> (near the bottom of the page). After 220 lines of seemingly successful processing, I got an error copied below. I hit <enter> a few times, and the "pdflatex" finished, apparently successfully. Comments? Thanks,

On a CentOS 7 machine, I am at a loss with respect to an inability to run a full R CMD check as anything involving tex files ends in tears. We followed the README at CRAN and installed a large number of tex-live packages on this machine. But when a manual is created, we end up with what follows below. Here, I chopped some of the error messages, the key seems to be 'Insufficient extension

On 29 May 2018 at 16:37, R P Herrold wrote: | On Tue, 29 May 2018, Dirk Eddelbuettel wrote: | | > On a CentOS 7 machine, I am at a loss with respect to an inability to run a | > full R CMD check as anything involving tex files ends in tears. | | Hi, Dirk | | Have fun at the upcoming conference at UIC | | I seem to have 56 font packages installed under CentOS 7 | locally, but then I work

On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: > I noticed it with a local, not-public package -- but it appears to apply with > any source package. I replicated with pkgKitten straight off CRAN and after > checking that it has a six page manual there. I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I can pull the pkgKitten source down, and run R CMD Rd2pdf

Tom, On 30 May 2018 at 11:34, Tom Callaway wrote: | On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: | > I noticed it with a local, not-public package -- but it appears to apply with | > any source package. I replicated with pkgKitten straight off CRAN and after | > checking that it has a six page manual there. | | I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I

Hi list, When using R CMD Rd2pdf, it is possible to set environment variable RD2PDF_INPUTENC to value "inputenx" and enjoy better support for UTF-8 characters (see ?Rd2pdf). This enables LaTeX package "inputenx" instead of "inputenc". Even better support for UTF-8 encoded characters can be had by better using the facilities provided by inputenx and making R CMD

On an new install of Ubuntu 8.10 64bit, I am having trouble with make check-all checking package 'survival' and elsewhere: l.100 \fontencoding\encodingdefault\selectfont ! LaTeX Error: File `kvoptions.sty' not found. Type X to quit or <RETURN> to proceed, or enter new name. (Default extension: sty) ! Emergency stop. <read *> l.2231

Hi all I am trying to build an R package, which I have successfully done many times before, but have an error I cannot trace. I hope someone can help me. Here's is some edited output (full output below if it is useful): pdunn2 at PDunnUbuntu:~/DSdata$ R CMD build GLMsData * checking for file 'GLMsData/DESCRIPTION' ... OK * preparing 'GLMsData': * checking DESCRIPTION

I have several old encapsulated postscript graphics generated by R that I want to include in a LaTeX Beamer presentation so I want them in pdf. Under Ubuntu linux typing convert z.eps z.pdf (to use ImageMagick) results in a nice looking graphic but the bounding box is lost. Doing convert z.eps z.epdf results in a fuzzy image with a good bounding box. Does anyone have a nice solution?

Hi everyone, Two minor points about ?.Renviron. 1) If R_ENVIRON is not set then R defaults to `${R_HOME}/etc/Renviron', not `${R_HOME}/etc/Renviron.site' as stated. 2) In the details, there is a missing "way" in "`value' is processed in a similar to a Unix shell." Cheers, Jonathan. --please do not edit the information below-- Version: platform =

As some of you will be aware, TeXLive 2009 was released last month having blocked updates on earlier versions since May. This has lead to a flood of updates of LaTeX packages, as a result of which the PDF manuals of R 2.10.0 and earlier will no longer build, for two separate reasons. For MiKTeX users: at least version 2.8 (the current one) has the same updates (a week or so later) and has