Re: [R] interfacing with .Call

2012-12-16 Thread Thomas Lumley
On Mon, Dec 17, 2012 at 8:02 AM, William Dunlap wrote: > The problem almost certainly lies in the parts of the code that you have > not shown, the R-language code including the .Call or, more likely in my > opinion, the C++ code for Projector. I would have blamed the unPROTECTed coerceVector()

Re: [R] interfacing with .Call

2012-12-16 Thread William Dunlap
The problem almost certainly lies in the parts of the code that you have not shown, the R-language code including the .Call or, more likely in my opinion, the C++ code for Projector. You can get different values in Projector's Lsum matrix if (a) Projector doesn't assign values to all of them (

Re: [R] interfacing with .Call

2012-12-16 Thread R. Michael Weylandt
On Sun, Dec 16, 2012 at 6:20 PM, Shangru Li wrote: > Hi > The function "Projector" works well and actually the interface with .C > works OK. > The question is that I can compile it in R, but ".Call" returns different > result each time with same inputs. Could anybody tell me why? Thanks! > I have