Re: [Rd] Unexpected failure when calling new() with unnamed arg and

> Joshua Wiley > on Thu, 8 Oct 2015 12:19:16 +1100 writes: > Hi, I realize this is an old thread, but just wondering > whether a conclusion was ever reached on this issue? I'm > using formula(NULL) but it would be nice if default >

Re: [Rd] Unexpected failure when calling new() with unnamed arg and

Hi Martin, Thanks and apologies for not seeing that. I had checked NEWS but not tried it in R devel. Thanks again. Josh On Thu, Oct 8, 2015 at 10:03 PM, Martin Maechler wrote: > > Joshua Wiley > > on Thu, 8 Oct 2015 12:19:16

Re: [Rd] authorship and citation

> > I read the CRAN policies twice, and there > > is no official guideline on how to compile the citation. The policies are about copyright and IP, not credited authorship. There's overlap but they are not the same thing. You can see whether someone is a copyright holder by referring to the

Re: [R-pkg-devel] Diagnosing error on CRAN's old R, old Windows

My intent wasn't particularly to blame CRAN, just puzzlement that a normally-chatty test script is silently dying in this one case. Anyway, thanks for the advice. Ben On Thu, Oct 8, 2015 at 8:43 AM, Duncan Murdoch wrote: > On 08/10/2015 8:06 AM, Ben Bond-Lamberty

Re: [Rd] authorship and citation

S Ellison posted: (quoting someone else, it appears) I read the CRAN policies twice, and there is no official guideline on how to compile the citation. And once again Dr Ellison is not attributing quotes: that is clearly covered by the posting guide. Including: Take care when you quote

Re: [R-pkg-devel] Diagnosing error on CRAN's old R, old Windows

>Unfortunately the error diagnostics are not particularly helpful, only showing >that four tests failed; the only common thread I see, maybe, is that all four >tests--and no others--use R's file.size() function. Brief follow-up for completeness: it turns out that `file.size()` doesn't exist on

[Rd] library() in .Rd Examples (Depends vs. Imports)?

I'm a little confused when documenting my code using Imports vs. Depends. If I have an example in my .Rd that uses a library that is listed under Imports, it doesn't work, but if it is listed under Depends, it does. What is the proper way to go about using examples that rely on an Imports? Should

Re: [Rd] library() in .Rd Examples (Depends vs. Imports)?

On 08/10/2015 1:51 PM, Jonathan Greenberg wrote: I'm a little confused when documenting my code using Imports vs. Depends. If I have an example in my .Rd that uses a library that is listed under Imports, it doesn't work, but if it is listed under Depends, it does. What is the proper way to go

[Rd] R-core package cross compilation help

Hi, I am a beginner to R language and currently exploring R to use it for machine learning use case. My requirement is to include R-core package in my embedded linux box which runs on customized Monta Vista Linux with kernel 2.6.32 and it has multi-core MIPS processor. I hope, there is NO

Re: [R-pkg-devel] how to make "r-release-osx-x86_64-mavericks" machine support rgl 3D plots

On 08/10/2015 4:41 PM, Dr Gregory Jefferis wrote: > Dear Duncan, > > Could I just revive this one more time > > On 16 Aug 2015, at 17:21, Duncan Murdoch wrote: > >> It is harder for you to implement this yourself, because CRAN frowns >> on >> tests that try to detect whether they're running

Re: [Bioc-devel] Moderating "answers" into comments on other answers/comments on the support site?

- Original Message - > From: "Michael Lawrence" > To: "Dan Tenenbaum" > Cc: "Ryan C. Thompson" , bioc-devel@r-project.org > Sent: Thursday, October 8, 2015 2:05:51 PM > Subject: Re: [Bioc-devel] Moderating

Re: [Rd] R-core package cross compilation help

On Thu, 2015-10-08 at 13:58 -0700, Sasikumar Kandhasamy wrote: > I am a beginner to R language and currently exploring R to use it for > machine learning use case. My requirement is to include R-core package in > my embedded linux box which runs on customized Monta Vista Linux with > kernel 2.6.32

[Rd] rank(, ties.method="last")

Hi, I ran into a problem where I actually need rank(, ties.method="last"). It would be great to have this feature in base and it's also simple to get (see below). Thanks & cheers, Marius rank2 <- function (x, na.last = TRUE, ties.method = c("average", "first", "last", # new "last"

Re: [Bioc-devel] Moderating "answers" into comments on other answers/comments on the support site?

With regard to moderation of this, see the issue I reported a while ago: https://github.com/ialbert/biostar-central/issues/353. On Thu, Oct 8, 2015 at 1:15 PM, Dan Tenenbaum wrote: > Hi Ryan, > > - Original Message - > > From: "Ryan C. Thompson"

Re: [R-pkg-devel] how to make "r-release-osx-x86_64-mavericks" machine support rgl 3D plots

Dear Duncan, Could I just revive this one more time On 16 Aug 2015, at 17:21, Duncan Murdoch wrote: It is harder for you to implement this yourself, because CRAN frowns on tests that try to detect whether they're running under CRAN or not. You could put in "if (interactive())" checks around

Re: [Rd] R 3.2.2 64 bit compilation error on AIX

Ahh, sorry for not googling the error message. Found [this](http://r.789695.n4.nabble.com/Error-compiling-R-2-10-1-on-AIX-td1017862.html) post that suggests modifying /src/extra/tre/tre-internal.h (https://r-forge.r-project.org/scm/viewvc.php/patches/aix_R210_tre.patch?view=markup=aix) for AIX 64

Re: [R-pkg-devel] how to make "r-release-osx-x86_64-mavericks" machine support rgl 3D plots

On 08/10/2015 7:55 PM, Ott Toomet wrote: > Alternatively, you can exclude selected tests from being included in the > package. Most of the tests I do are not necessary to run on CRAN, these > are not system dependent while still time consuming. To run these just > on my PC in enough. So I use

Re: [Rd] R 3.2.2 64 bit compilation error on AIX

Please note that if I don't specify those variables, then R 32 bit compiles fine. Thanks. -- Vinh On Thu, Oct 8, 2015 at 6:50 PM, Vinh Nguyen wrote: > Dear list, > > I'm following the instructions provided here to compile R 64 bit on > AIX 6.1. I did > > export

Re: [Rd] R 3.2.2 64 bit compilation error on AIX

One other note: I'm also using the latest src/main/dcf.c that was giving an issue on AIX previously; see [this](https://stat.ethz.ch/pipermail/r-devel/2015-September/071781.html) thread. Thanks. On Thu, Oct 8, 2015 at 6:51 PM, Vinh Nguyen wrote: > Please note that if I

[Rd] R 3.2.2 64 bit compilation error on AIX

Dear list, I'm following the instructions provided here to compile R 64 bit on AIX 6.1. I did export OBJECT_MODE=64 export CC="gcc -maix64 -pthread" export CXX="g++ -maix64 -pthread" export FC="gfortran -maix64 -pthread" export F77="gfortran -maix64 -pthread" export CFLAGS="-O2 -g -mcpu=power6"

Re: [R-pkg-devel] how to make "r-release-osx-x86_64-mavericks" machine support rgl 3D plots

Alternatively, you can exclude selected tests from being included in the package. Most of the tests I do are not necessary to run on CRAN, these are not system dependent while still time consuming. To run these just on my PC in enough. So I use .Rbuildignore to exclude those. Cheers, Ott On

[Rd] Building manuals are failing now that MikTex 2.9 has removed texi2dvi.exe

According to the MikTex bug reports [1], MikTex 2.9 has removed texi2dvi.exe last week (on 2015-09-29) as "it was not compatible (anymore) with the original shell script texi2dvi (GNU Texinfo)." I found this out the hard way as I just (unknowingly) updated MikTex this evening, and then, while

Re: [Rd] Building manuals are failing now that MikTex 2.9 has removed texi2dvi.exe

On Fri, Oct 9, 2015 at 1:44 AM, Prof Brian Ripley wrote: > Hmm, look in MkRules.dist for the setting you failed to make Obviously > available in R-patched and R-devel only as we cannot foretell such changes. > >[snip] Yes, I see my error. For efficiency, I had copied

Re: [Rd] Building manuals are failing now that MikTex 2.9 has removed texi2dvi.exe

Hmm, look in MkRules.dist for the setting you failed to make Obviously available in R-patched and R-devel only as we cannot foretell such changes. On 09/10/2015 06:24, Avraham Adler wrote: According to the MikTex bug reports [1], MikTex 2.9 has removed texi2dvi.exe last week (on

Re: [Rd] names treatment in optim()

Dear list, A possible patch to correct the treatment of names consists in adding the following lines if(!is.null(names(par))) names(res$par) <- names(par) if(!is.null(names(fn1(par names(res$value) <- names(fn1(par)) just before returning the variable res in optim. That is