Re: [Rd] [R] factanal AIC?

2007-05-04 Thread Spencer Graves
Dear R Developers: What is the proper log(likelihood) for 'factanal'? I believe it should be something like the following: (-n/2)*(k*(log(2*pi)+1)+log(det(S))) or without k*(log(2*pi)-1): (-n/2)*log(det(S)), where n = the number of (multivariate) observations. Th

Re: [Rd] sending signals to embedded R

2007-05-04 Thread Luke Tierney
On Fri, 4 May 2007, Deepayan Sarkar wrote: > On 5/4/07, Prof Brian Ripley <[EMAIL PROTECTED]> wrote: >> On Fri, 4 May 2007, Deepayan Sarkar wrote: >> >>> one thing I haven't been able to figure out from R-exts is how to >>> interrupt a calculation running inside an embedded R. C code inside R >>>

Re: [Rd] sending signals to embedded R

2007-05-04 Thread Deepayan Sarkar
On 5/4/07, Prof Brian Ripley <[EMAIL PROTECTED]> wrote: > On Fri, 4 May 2007, Deepayan Sarkar wrote: > > > one thing I haven't been able to figure out from R-exts is how to > > interrupt a calculation running inside an embedded R. C code inside R > > calls R_CheckUserInterrupt() intermittently to c

Re: [Rd] sending signals to embedded R

2007-05-04 Thread Prof Brian Ripley
On Fri, 4 May 2007, Deepayan Sarkar wrote: > one thing I haven't been able to figure out from R-exts is how to > interrupt a calculation running inside an embedded R. C code inside R > calls R_CheckUserInterrupt() intermittently to check for interrupts, > but how does my GUI tell R that the user w

[Rd] sending signals to embedded R

2007-05-04 Thread Deepayan Sarkar
Hi, one thing I haven't been able to figure out from R-exts is how to interrupt a calculation running inside an embedded R. C code inside R calls R_CheckUserInterrupt() intermittently to check for interrupts, but how does my GUI tell R that the user wants it interrupted? -Deepayan __

Re: [Rd] Qt device update

2007-05-04 Thread Prof Brian Ripley
On Fri, 4 May 2007, Simon Urbanek wrote: > > On May 3, 2007, at 8:52 PM, Deepayan Sarkar wrote: > >> [...] I have a couple of related questions. First, dev.interactive >> (), used in example() and many demo()-s to decide if the current >> device is interactive, is currently implemented as: >> >>>

Re: [Rd] Qt device update

2007-05-04 Thread Deepayan Sarkar
On 5/3/07, Prof Brian Ripley <[EMAIL PROTECTED]> wrote: > On Thu, 3 May 2007, Deepayan Sarkar wrote: > > > Hi, > > > > a few days back I had asked for help on a Qt device package. Thanks to > > hints from Duncan TL and Thomas Friedrichsmeier, I now have something > > more or less functional. For th

[Rd] Bug in qr.R ? (PR#9655)

2007-05-04 Thread Dietrich . Trenkler
Ladies and Gentlemen, using > A <- structure(c(1, 0, 0, 3, 2, 1, 4, 5, -3, -2, 1, 0), .Dim = as.integer(c(3,4))) I get > dim(A) [1] 3 4 > qr.R(qr(A),complete=TRUE) [,1] [,2] [,3] [,4] [1,] -1 -3.00 -4.00 2.000 [2,]0 -2.236068 -3.130495 -0.8944272 [3

Re: [Rd] Qt device update

2007-05-04 Thread Simon Urbanek
On May 3, 2007, at 8:52 PM, Deepayan Sarkar wrote: > [...] I have a couple of related questions. First, dev.interactive > (), used in example() and many demo()-s to decide if the current > device is interactive, is currently implemented as: > >> dev.interactive > function (orNone = FALSE) > {

Re: [Rd] Imports/exports of S4 methods

2007-05-04 Thread Paul Gilbert
I'm wrestling with the same issues, so this is the blind leading the blind, but that usually prompts someone knowledgeable to say something useful. Roger D. Peng wrote: >I have a question about what to do in the following situation (please bear >with >the setup): > >Package A defines an S4 g

[Rd] Display list redraw incomplete

2007-05-04 Thread Roger Peng
Since compiling R 2.5.0 from source on my Mac (PowerBook) I've noticed some strange behavior when plotting. I'm not sure if it's a problem with my setup/compilation because I feel like a problem as basic as this one would have been reported already. I'm running R with X11 and R was built with gcc

Re: [Rd] R CMD Rdconv drops sections: arguments, seealso, examples (PR#9649)

2007-05-04 Thread Prof Brian Ripley
On Thu, 3 May 2007, Prof Brian Ripley wrote: > Bill, > > Now we have access again to the R-bugs repository (the database has been > offline for about a week) I can try to understand this. > > This is a follow up to PR#9645 which was itself a follow up to PR#9606, > which was a report that Rdconv s