Peter wrote: > On Wed, Jul 22, 2009 at 10:00 PM, Skipper Seabold<jsseab...@gmail.com> wrote: >> Thanks for the reply. I have a wrapper for RPy that makes the >> interface similar to some statistical models code that I am working on >> for SciPy, and this is how the bug comes up. The weird thing that I >> discovered in trying to replicate is that it only comes up when x is >> defined from another source and only for psi.hampel, even though it is >> *exactly* the same as the x below. Very frustrating and odd. I can't >> think of anything that would make the x array that I have different >> from the one defined below. ... > > Since x is a NumPy array these can come in different flavours, and > perhaps something here is breaking rpy2 or R, e.g.
The bug report if for rpy-1.0.x, I think. I did not dare asking if using rpy2 would solve the problem, but since you are bringing rpy2 into into the picture... L. > * Contiguous in memory or non-contiguous > * C order versus Fortran order > * Owns the memory or doesn't (e.g. a view onto another array) > * Precise data type (e.g. signed versus unsigned, or the precision) > > I would try making an explicit copy of x to rule some of these issues. > > Peter ------------------------------------------------------------------------------ _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
