[Rpy] [ rpy-Support Requests-2721281 ] RPy2 with Fink's R: no LAPACK_LIBS; setup.py fails

2009-04-04 Thread SourceForge.net
Support Requests item #2721281, was opened at 2009-03-29 23:21 Message generated for change (Comment added) made by lgautier You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=453022&aid=2721281&group_id=48422 Please note that this message will contain a full copy of t

Re: [Rpy] rpy2 vector length limitation? - workaround

2009-04-04 Thread Laurent Gautier
Joel, Good that you solved your issue. However, I am not certain of what you mean by "extracting the required object directly from the address rather than first converting the address to a string". Self-contained examples often constitute a very efficient way to demonstrate the problem when re

Re: [Rpy] rpy2 vector length limitation?

2009-04-04 Thread Laurent Gautier
Joel Neilson wrote: (...) > > I've checked all my inputs and everything is peachy on the Python > side. Given the high correlation of the bug with the vector length, I > think the most likely explanations are the following: > > (1) vector is too long and this causes some breakdown when R an

Re: [Rpy] rpy2 vector length limitation? - workaround

2009-04-04 Thread Joel Neilson
No problem - I apologize for the lack of clarity. >>> import rpy2.robjects as robjects >>> r = robjects.r >>> wilcox = robjects.r['wilcox.test'] >>> vec1 = [1,2,3,4,5] >>> vec2 = [4,5,6,7,8] >>> rvec1 = robjects.FloatVector(vec1) >>> rvec2 = robjects.FloatVector(vec2) >>> address = wilcox(

Re: [Rpy] rpy2 vector length limitation? - workaround

2009-04-04 Thread Laurent Gautier
Joel Neilson wrote: > No problem - I apologize for the lack of clarity. > > >>> import rpy2.robjects as robjects > >>> r = robjects.r > >>> wilcox = robjects.r['wilcox.test'] > >>> vec1 = [1,2,3,4,5] > >>> vec2 = [4,5,6,7,8] > >>> rvec1 = robjects.FloatVector(vec1) > >>> rvec2 = robjects.Fl