Re: [Rd] using rasterImage within image

2011-02-11 Thread Michael Sumner
Hello, that appears to have fixed it. Thank you very much. I can now repeat the reported workflow and the image appears on the fifth (and subsequent) calls. Cheers, Mike. sessionInfo() R version 2.13.0 Under development (unstable) (2011-02-11 r54330) Platform: x86_64-pc-mingw32/x64 (64-bit) lo

Re: [Rd] R limits documented?

2011-02-11 Thread David Winsemius
On Feb 11, 2011, at 8:46 PM, Simon Urbanek wrote: On Feb 11, 2011, at 8:45 PM, Simon Urbanek wrote: On Feb 11, 2011, at 7:55 PM, David Winsemius wrote: On Feb 11, 2011, at 7:09 PM, Dominick Samperi wrote: Is there documentation on R limits? That is, max matrix size, etc.? Diagnostics

Re: [Rd] R limits documented?

2011-02-11 Thread Simon Urbanek
On Feb 11, 2011, at 8:45 PM, Simon Urbanek wrote: > > On Feb 11, 2011, at 7:55 PM, David Winsemius wrote: > >> >> On Feb 11, 2011, at 7:09 PM, Dominick Samperi wrote: >> >>> Is there documentation on R limits? >>> That is, max matrix size, etc.? >>> >>> Diagnostics when limits are exceeded a

Re: [Rd] R limits documented?

2011-02-11 Thread Simon Urbanek
On Feb 11, 2011, at 7:55 PM, David Winsemius wrote: > > On Feb 11, 2011, at 7:09 PM, Dominick Samperi wrote: > >> Is there documentation on R limits? >> That is, max matrix size, etc.? >> >> Diagnostics when limits are exceeded are not always >> meaningful. For example: >>> x <- rep(0,5*50

Re: [Rd] R limits documented?

2011-02-11 Thread David Winsemius
On Feb 11, 2011, at 7:09 PM, Dominick Samperi wrote: Is there documentation on R limits? That is, max matrix size, etc.? Diagnostics when limits are exceeded are not always meaningful. For example: x <- rep(0,5*5) Error in rep(0, 5 * 5) : invalid 'times' argument In addition:

[Rd] R limits documented?

2011-02-11 Thread Dominick Samperi
Is there documentation on R limits? That is, max matrix size, etc.? Diagnostics when limits are exceeded are not always meaningful. For example: > x <- rep(0,5*5) Error in rep(0, 5 * 5) : invalid 'times' argument In addition: Warning message: In as.vector(data) : NAs introduced by

Re: [Rd] Writting my own package - 64 bit problem with R_GetCCallable

2011-02-11 Thread Ryan King
Ah thanks, that did fix it. Ryan King On Fri, Feb 11, 2011 at 3:53 PM, Simon Urbanek wrote: > Ryan, > > On Feb 11, 2011, at 4:29 PM, Ryan King wrote: > >> Hello list, >> I've been working on a package of my own.  It works fine on the 32bit >> linux machines that I've tested it on.  Someone using

Re: [Rd] read.csv trap

2011-02-11 Thread Ben Bolker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/11/2011 03:37 PM, Laurent Gatto wrote: > On 11 February 2011 19:39, Ben Bolker wrote: >> > [snip] >> >> What is dangerous/confusing is that R silently **wraps** longer lines if >> fill=TRUE (which is the default for read.csv). I encountered thi

Re: [Rd] Writting my own package - 64 bit problem with R_GetCCallable

2011-02-11 Thread Simon Urbanek
Ryan, On Feb 11, 2011, at 4:29 PM, Ryan King wrote: > Hello list, > I've been working on a package of my own. It works fine on the 32bit > linux machines that I've tested it on. Someone using 64bit ubuntu > wanted to try it, and surprising segfaults happened. My test code > results in no segfa

[Rd] Writting my own package - 64 bit problem with R_GetCCallable

2011-02-11 Thread Ryan King
Hello list, I've been working on a package of my own. It works fine on the 32bit linux machines that I've tested it on. Someone using 64bit ubuntu wanted to try it, and surprising segfaults happened. My test code results in no segfault, errors, or leaks from my calls when run under valgrind (I r

Re: [Rd] read.csv trap

2011-02-11 Thread Laurent Gatto
On 11 February 2011 19:39, Ben Bolker wrote: > [snip] > > What is dangerous/confusing is that R silently **wraps** longer lines if > fill=TRUE (which is the default for read.csv).  I encountered this when > working with a colleague on a long, messy CSV file that had some phantom > extra fields in

Re: [Rd] read.csv trap

2011-02-11 Thread Ken.Williams
On 2/11/11 1:39 PM, "Ben Bolker" wrote: >[snip] > Original Message >Subject: read.csv trap >Date: Fri, 04 Feb 2011 11:16:36 -0500 >From: Ben Bolker >To: r-de...@stat.math.ethz.ch , David Earn > > >[snip] >What is dangerous/confusing is that R silently **wraps** longer lines i

Re: [Rd] read.csv trap

2011-02-11 Thread Ben Bolker
Bump. It's been a week since I posted this to r-devel. Any thoughts/discussion? Would R-core be irritated if I submitted a bug report? cheers Ben Original Message Subject: read.csv trap Date: Fri, 04 Feb 2011 11:16:36 -0500 From: Ben Bolker To: r-de...@stat.math.

Re: [Rd] Problem with confint function

2011-02-11 Thread peter dalgaard
On Feb 11, 2011, at 19:25 , Kino Aguilar wrote: > Hi, > > I am currently doing logistic regression analyses and I am trying to get > confidence intervals for my partial logistic regression coefficients. > Supposing I am right in assuming that the formula to estimate a 95% CI for a > log odds coe

Re: [Rd] Problem with confint function

2011-02-11 Thread John Fox
Dear Kino, The confidence intervals that you've computed yourself are based on the Wald statistic, while confint() computes confidence intervals based on the likelihood-ratio statistic, by profiling the likelihood (see ?confint and click on the link for confint.glm). Basing confidence intervals on

[Rd] Problem with confint function

2011-02-11 Thread Kino Aguilar
Hi, I am currently doing logistic regression analyses and I am trying to get confidence intervals for my partial logistic regression coefficients. Supposing I am right in assuming that the formula to estimate a 95% CI for a log odds coefficient is the following: log odds - 1.96*SE to log odds + 1

Re: [Rd] R project testers - how to help out

2011-02-11 Thread Prof Brian Ripley
We have a 4-week alpha/beta/RC period every 6 months for testing before a 2.x.0 release. This is announced here, and we get very little response. I expect the testing window for R 2.13.0 to be Mar-Apr. That said, we do quite extensive testing on the main platforms (ix86 and x86_64 Linux, i3