I'm working through the list of bugs / patches /feature enhancements
now....
-G
On Oct 8, 2007, at 9:13AM , Dirk Eddelbuettel wrote:
>
> Greg,
>
> On 3 October 2007 at 11:27, Gregory Warnes wrote:
> |
> | Hi Dirk, Alan, et al.
> |
> | Sorry for the huge delay in response. I'll look into this by the
> end
> | of the week.
>
> Did you get a chance to look at this?
>
> Thanks, Dirk
>
>
> | -G
> |
> | On Oct 3, 2007, at 10:12AM , Dirk Eddelbuettel wrote:
> |
> | >
> | > ( Greg: PLEASE PLEASE PLEASE follow-up, see the Q at the bottom)
> | >
> | > Hi Allen,
> | >
> | > Thanks for the detailed follow-up!
> | >
> | > On 3 October 2007 at 08:47, Allen Chan wrote:
> | > | On Tuesday 02 October 2007, Dirk Eddelbuettel wrote:
> | > | > Greg,
> | > | >
> | > | > Comments from you would still be appreciated.
> | > | >
> | > | > Allen,
> | > | >
> | > | > Anything new from your end?
> | > | >
> | > | >
> | > | > Thanks, Dirk
> | > | >
> | > |
> | > | Dirk,
> | > |
> | > | I've simplified the test case a little bit to help testing:
> | > |
> | > | from rpy import *
> | > |
> | > | x = [-5.0, -3.0, 3.0, 5.0]
> | > | y = [-5.0, -3.0, 3.0, 5.0]
> | > | z = array([[ 0.4, 0.3, 0.3, 0.4],
> | > | [ 0.3, 0.0, 0.0, 0.3],
> | > | [ 0.3, 0.0, 0.0, 0.3],
> | > | [ 0.4, 0.3, 0.3, 0.4]])
> | > | r.png("image.png", bg="transparent")
> | > | r.persp(x, y, z, theta = -15, phi = 35)
> | > |
> | > | This exhibits similiar behavior as the original test case:
> | > |
> | > | RHOME= /usr/lib/R
> | > | RVERSION= 2.6.0
> | > | RVER= 2060
> | > | RUSER= /home/user
> | > | Loading Rpy version 2060 .. Done.
> | > | Creating the R object 'r' .. Done
> | > | Warning messages:
> | > | 1: In min(x) : no non-missing arguments to min; returning Inf
> | > | 2: In max(x) : no non-missing arguments to max; returning -Inf
> | > | Traceback (most recent call last):
> | > | File "persp2.py", line 11, in ?
> | > | r.persp(x, y, z, theta = -15, phi = 35)
> | > | rpy.RException: Error in persp.default(c(-5, -3, 3, 5), c(-5,
> | > -3, 3, 5), NULL, theta = -15L, :
> | > | invalid 'z' argument
> | > |
> | > | This still works fine under i386, and under amd64 with
> | > | python-rpy 1.0~rc2-1 or earlier. It fails under amd64 with
> | > | python-rpy 1.0~rc3-1 or later.
> | >
> | > Ok. One thing I could imagine is that the R / Python object
> | > mapping shoots
> | > itself in the foot with amd64. I am not really a user of RPy and
> | > rusty with
> | > its details, but what happens when you specify a different
> conversion?
> | >
> | > | I also took the python-rpy 1.0~rc3-1 sources, hand
> | > | modified setup.py, rpy.py, and debian/control to force
> | > | it to compile and run with numeric instead of numpy
> | > | under amd64, and the problem went away. I am not
> | >
> | > Good stuff.
> | >
> | > | familiar enough with the numpy and numeric
> | > | implementations to figure out which part of the numeric
> | > | to numpy conversion code is causing the problem. I
> | > | would gladly recompile and do some testing and
> | > | debugging if someone would give me some hints on
> | > | what to look for.
> | >
> | > Not being a Python programmer, I also get lost in the alphabet
> soup
> | > between
> | > (old) Numpy, Numeric, Numarray, (new) Numpy.
> | >
> | > Greg: What should we use here for x86 and amd64 compatibility?
> | >
> | > Dirk
> | >
> | > --
> | > Three out of two people have difficulties with fractions.
> |
>
> --
> Three out of two people have difficulties with fractions.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
rpy-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rpy-list
