similar to: putting match.call to good use

Hi, I have spent a few hours on the R-exts manual and the documentation of parse_Rd() (as well as the PDF document in the references), but I still have not figured out what results=rd means. I thought I could use an R code fragment to create an Rd fragment dynamically. Here is an example, in which I was expected the output to be a describe list <DL> in HTML, but it turns out not to be true.

Dear developers, I came across with a bug while parsing Rd files. Given is the following minimal Rd file: ---- \name{foo} \title{foo} \description{ #ifdef windows win #endifd #ifdef unix unix #endif } ---- By accident I have a typo at line 6, instead of having #endif I typed #endifd. If I run checkRd(), parse_Rd(), Rd2HTML(), or others including the command line "R CMD Rconv" R

Hi All, I've been having a little trouble with creating a loop that will run a a series of t.tests for inspection, Below is the code i've tried, and some checks i've looked at. I've used the get(paste()) idea as i was told previously that the use of the eval should try and be avoided. I've run a single syntax to check that my systax is correct and works without any problems

I have installed the arm package and its dependents (e.g MATRIX, etc), but cannot use the functions "invlogit" and "bayesglm" because it gives me the error message "Error: could not find function "invlogit" or Error: could not find function "invlogit". What could be the problem. Regards Carrington [[alternative HTML version deleted]]

Hi R bayesians, I need an advise how to resolve the two different estimates applying a traditional glm (TG) and a bayes glm (BG), and different results depending on the data formats of response data and the prior specs using bayesglm in R. I'm not familiar with bayes estimate and my colleague asked me to look into this because the EPA from France reported a quite different estimates for

Dear list, I've noticed that, when writing examples in an Rd file, you need to escape the '%' character, even if it is valid R code. I can see maybe this is the intended behaviour, but I found it a bit surprising, and leads to cryptic error messages from 'R CMD check'. The relevant section in the "writing R extensions" manual isn't clear on that point either. To

iterations <- 100 nvars <- 4 combined <- rbind(scaleMiceTrain, scaleMiceTest) reducedSample <- combined reducedSample <- subset(reducedSample, select = -pID50) reducedSample <- subset(reducedSample, select = -id) for (i in 1:iterations) { miceSample <- sample(combined[,-c(1,2)],nvars, replace=FALSE) miceSample$pID50 <- combined$pID50 miceTestSample <-

Could someone advise me about how to react to the message: * checking R code for possible problems ... NOTE slm: no visible binding for global variable 'response' from R CMD check SparseM with * using R version 2.6.0 Under development (unstable) (2007-09-03 r42749) The offending code looks like this: "slm" <- function (formula, data, weights, na.action, method =

When I run R CMD Rd2pdf on the man pages of a package, ie R CMD Rd2pdf man I get Converting Rd files to LaTeX Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, : man/mpra-package.Rd:6: unknown macro '\packageTitle' Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, :

Bug or feature? I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, eg \mymacro{}: Error in tools::parse_Rd(fn) : Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but

While on the topic of Rd macro arguments, it seems that if a multiline argument is supplied, the lines after the first are silently ignored: f <- tempfile() mac6 <- "\\newcommand{\\mac6}{mac6: #1}" cat(mac6, "\\mac6{2*3 2+2 sin(pi) }\n", file = f) rd <- tools::parse_Rd(f) > rd mac6: 2*3 --- Georgi Boshnakov -----Original Message----- From: Tomas Kalibera

I was writing Rd documentation for a new package when I came across this issue. Here's the smallest example: > library(tools) > cat("\\examples{x <- '<%=rnorm(1)%>'}\n",file=file.path(tempdir(),'test.Rd')) > readLines(file.path(tempdir(),'test.Rd')) [1] "\\examples{x <- '<%=rnorm(1)%>'}" >

No, I do not get the same as you. I have tested with R-devel and R-patched compiled today. When I do R CMD Rd2pdf mpra I get (as reported a few days ago) Hmm ... looks like a package Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file './DESCRIPTION' does not exist whereas you (Kurt) reports that this works on zTree. When I do R CMD Rd2pdf mpra/man I get - a

Hi (Duncan?), The other day I noticed some characters will cause errors in R CMD CHECK because of parse_Rd(), and AFAIK, these chars include '%', '{' and '}'. For example, note the comments in the example section: %~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~% \name{testfun} \Rdversion{1.1} \alias{testfun} \title{ A Test } \description{ A test } \usage{ testfun() } \value{ NULL }

With a pretty recent version of R 2.11.0 (devel,unstable, svn 50178) on Linux I could not install version 1.5-8 of zoo (the current on on CRAN): % R-devel CMD INSTALL -l Rlib3 zoo * installing *source* package 'zoo' ... ** R ** inst ** preparing package for lazy loading ** help *** installing help indices converting help for package 'zoo' finding

I'm trying to use stepAIC on sparse matrices, and I need some help. The documentation for slm.fit suggests: slm.fit and slm.wfit call slm.fit.csr to do Cholesky decomposition and then backsolve to obtain the least squares estimated coefficients. These functions can be called directly if the user is willing to specify the design matrix in matrix.csr form. This is often advantageous in large

Hello Andy, Thank you for your offer to work together on implementing the your new scheduler on X86. I can start working on this right away. In case you were unaware, the new Silvermont micro-architecture is only out of order on the integer side. The SSE instructions are still in order, so the current postRA scheduler is very beneficial for code with lots of SSE instructions, such as the ISPC

Hi All, I created a two variable lm() model slm<-lm(y[1:3000,8]~y[1:3000,12]+y[1:3000,15]) I made two predictions predict(slm,newdata=y[201:3200,]) predict(slm,newdata=y[601:3600,]) there is no error message for either of these. the results are identical, and identical to slm$fitted as well. if this is not the right way to apply the model coefficients to a new set of inputs, what is

I am in the process of submitting a package to CRAN. R CMD check ran successfully on the package on my local computer, using R version 2.1.1. However, on the computers for CRAN (with version 2.10.0), the following errors occurred: Warning in parse_Rd("./man/predict.Rd", encoding = "unknown") : ./man/predict.Rd:28: unknown macro '\dquote' *** error on file

Buenos días, estoy intentando reproducir el script de este github: http://uc-r.github.io/iml-pkg#interactions Todo iba bien hasta que en el 6º panel me encuentro esto: For any given loss function do 1: compute loss function for original model 2: for variable i in {1,...,p} do | randomize values | apply given ML model | estimate loss function | compute feature importance