Re: [Rd] As a package author, is there a way to specify that your package is architecture (x86_64) specific?

2011-09-08 Thread Steve Lianoglou
Hi Simon, Thanks for the quick response. Comments in line: On Thu, Sep 8, 2011 at 4:11 PM, Simon Urbanek wrote: > > On Sep 8, 2011, at 3:59 PM, Steve Lianoglou wrote: > >> Hi, >> >> Essentially: subject line says it all. >> >> I've created a package that wraps an external c++ library (which I d

[Rd] nobs(lm(...)) != nobs(glm(...)) when there are 0s in weights

2011-09-08 Thread William Dunlap
What is the rationale for nobs.lm omitting observations with zero weights while nobs.glm includes them? > df <- data.frame(x1=log(1:10), x2=1/(1:10), y=1:10, > wt=c(0,2,0,4,0,6,7,8,9,10)) > nobs(lm(data=df, y~x1+x2, weights=wt)) [1] 7 > nobs(glm(data=df, y~x1+x2, weights=wt)) [1] 10 The anova me

Re: [Rd] As a package author, is there a way to specify that your package is architecture (x86_64) specific?

2011-09-08 Thread Simon Urbanek
On Sep 8, 2011, at 3:59 PM, Steve Lianoglou wrote: > Hi, > > Essentially: subject line says it all. > > I've created a package that wraps an external c++ library (which I didn't > write) that only successfully compiles on 64bit machines. > That doesn't sound right, it contradicts your subjec

Re: [Rd] As a package author, is there a way to specify that your package is architecture (x86_64) specific?

2011-09-08 Thread Steve Lianoglou
Quick follow up before I get RTFM'd: I just found I can do: R CMD INSTALL --no-multiarch mypackage To get this to successfully work from the command line, so apologies for the second part of the question. The first Q remains, which is to either get this to happen "automagically" via Makevars, o

[Rd] As a package author, is there a way to specify that your package is architecture (x86_64) specific?

2011-09-08 Thread Steve Lianoglou
Hi, Essentially: subject line says it all. I've created a package that wraps an external c++ library (which I didn't write) that only successfully compiles on 64bit machines. I'd like to make the package broadly available, but is there a way to get it on CRAN if the 32-bit builds break by specif

Re: [Rd] repeatable segfault - on Mac

2011-09-08 Thread Rob Goedman
It is intermittent on both my systems. Rob On Sep 8, 2011, at 8:00 AM, luke-tier...@uiowa.edu wrote: > On Thu, 8 Sep 2011, Martin Maechler wrote: > >>> Simon Urbanek >>>on Thu, 8 Sep 2011 09:33:23 -0400 writes: >> >> > On Sep 8, 2011, at 4:01 AM, Martin Maechler wrote: >>

Re: [Rd] repeatable segfault - on Mac

2011-09-08 Thread luke-tierney
On Thu, 8 Sep 2011, Martin Maechler wrote: Simon Urbanek on Thu, 8 Sep 2011 09:33:23 -0400 writes: > On Sep 8, 2011, at 4:01 AM, Martin Maechler wrote: >>> David Winsemius >>> on Tue, 6 Sep 2011 00:38:13 -0400 writes: >> >>> I can reproduce: >>> eigen(crossprod

Re: [Rd] repeatable segfault - on Mac

2011-09-08 Thread Martin Maechler
> Simon Urbanek > on Thu, 8 Sep 2011 09:33:23 -0400 writes: > On Sep 8, 2011, at 4:01 AM, Martin Maechler wrote: >>> David Winsemius >>> on Tue, 6 Sep 2011 00:38:13 -0400 writes: >> >>> I can reproduce: >>> eigen(crossprod(matrix(1:2000, 50)) + (0+0i

Re: [Rd] repeatable segfault - on Mac

2011-09-08 Thread Simon Urbanek
On Sep 8, 2011, at 4:01 AM, Martin Maechler wrote: >> David Winsemius >>on Tue, 6 Sep 2011 00:38:13 -0400 writes: > >> I can reproduce: >> eigen(crossprod(matrix(1:2000, 50)) + (0+0i), T, T) > >> *** caught segfault *** >> address 0x102d0e028, cause 'memory not mapped' > >> Traceb

Re: [Rd] repeatable segfault - on Mac

2011-09-08 Thread peter dalgaard
On Sep 8, 2011, at 10:01 , Martin Maechler wrote: >> David Winsemius >>on Tue, 6 Sep 2011 00:38:13 -0400 writes: > >> I can reproduce: >> eigen(crossprod(matrix(1:2000, 50)) + (0+0i), T, T) > >> *** caught segfault *** >> address 0x102d0e028, cause 'memory not mapped' > >> Traceba

Re: [Rd] repeatable segfault - on Mac

2011-09-08 Thread Martin Maechler
> David Winsemius > on Tue, 6 Sep 2011 00:38:13 -0400 writes: > I can reproduce: > eigen(crossprod(matrix(1:2000, 50)) + (0+0i), T, T) > *** caught segfault *** > address 0x102d0e028, cause 'memory not mapped' > Traceback: > 1: .Call("La_rs_cmplx", x, only.va