Mailman 3 January 2006 - NumPy-Discussion

numpy.dot behavior with column vector and length 1 vector
by Brendan Simons 28 Jan '06

28 Jan '06

Is this behavior expected? If so, why am I wrong in assuming these statements should all return the same result? PyCrust 0.9.5 - The Flakiest Python Shell Python 2.4.1 (#2, Mar 31 2005, 00:05:10) [GCC 3.3 20030304 (Apple Computer, Inc. build 1666)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import numpy >>> colVect = numpy.ones((3, 1)) >>> colVect * 5.3 array([[ 5.3], [ 5.3], [ 5.3]]) >>> numpy.dot(colVect, 5.3) array([[ 5.3], [ 5.3], [ 5.3]]) >>> colVect * [5.3] array([[ 5.3], [ 5.3], [ 5.3]]) >>> numpy.dot(colVect, [5.3]) array([ 5.3, 0. , 0. ]) Brendan -- Brendan Simons __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 2

a virtual work party: help migrate scipy.org to new wiki
by Andrew Straw 28 Jan '06

28 Jan '06

As many of you know, a number of us have been busy migrating the scipy.org website to a new, more user-friendly wiki system. The new wiki is up-and-running, is more-up-to-date, and prettier-to-look at than the old site. We are working to make scipy.org a portal website for all scientific software written in Python, and not just for the packages numpy and scipy, which happen to have their natural homes there. This wiki structure allows peer-review-by-wiki, so please do not feel bashful about updating any aspect of the wiki to suit your opinions. The current address of the new site is http://new.scipy.org/Wiki Once we go "live", we'll point http://scipy.org to this wiki. Before we make the switch, however, there are a few things that need to be done and a few things that should be done. This is a request for two things: 1) Review the page http://new.scipy.org/Wiki/MigratingFromPlone and make sure you can live with what it says. If you can't edit it. 2) Please undertake any of the tasks listed at that page. Update the page that you're working on the task, and again when you're done. 3) (Optional) Bask in the glory of our shiny new website which will allow NumPy/ SciPy/ Matplotlib/ IPython/ whateverelse to rule the scientific computing world! I'd like to ask that we try and complete these tasks as quickly as possible. I know I'm asking a busy group of people to pitch in, but I hope you'll agree the results will be worth it. Thank you, Andrew Straw PS Sorry for the cross postings. I thought it would be important to get as many hands involved as possible.

2 2

array dtype=object problem
by Christopher Fonnesbeck 28 Jan '06

28 Jan '06

I am having trouble with numpy arrays that have (for some reason) an "object" dtype. All that happens in my code is that float values are appended to a multidimensional array, this array is transposed, and the transposed array is sent to matplotlib. Unfortunately, the array ends up being of type "object", which is not recognized by matplotlib: (Pdb) y[:5] array([575.060695363, 618.395159954, 817.767177867, 601.659726372, 978.607427424], dtype=object) (Pdb) scatter(x,y) *** TypeError: function not supported for these types, and can't coerce safely to supported types Moreover, this array, which clearly contains nothing but floats cannot be cast to a float array: (Pdb) array(y,float) *** TypeError: array cannot be safely cast to required type Can anyone shed some light on this? I am utterly confused. Thanks, C. -- Christopher J. Fonnesbeck Population Ecologist, Marine Mammal Section Fish & Wildlife Research Institute (FWC) St. Petersburg, FL Adjunct Assistant Professor Warnell School of Forest Resources University of Georgia Athens, GA T: 727.235.5570 E: chris at trichech.us

2 1

Linux Installation Instructions
by John Byrnes 28 Jan '06

28 Jan '06

Is anyone else unable to access the Linux install instructions at http://pong.tamu.edu/tiki/tiki-view_blog_post.php?blogId=6&postId=97 I get a 403 - Forbidden Page. Regards, John -- Well done is better than well said. -- Benjamin Franklin

2 1

RPy with NumPy
by Sasha 27 Jan '06

27 Jan '06

I have succesfully (according to testall.py :-) converted RPy to use numpy instead of Numeric. Attached patch was tested on Linux only. I did not attempt to create a package that would support both numpy and Numeric, but it is easy to do. Please let me know if you are interested. For numpy-discussion readers: "RPy is a very simple, yet robust, Python interface to the R Programming Language." <http://rpy.sourceforge.net/> For rpy-list readers: "Development for Numeric has ceased, and users should transisition to NumPy as quickly as possible." <http://numeric.scipy.org/> For readers of both lists: Sorry for cross-posting. -- sasha

1 0

Re: Fwd: [Numpy-discussion] Numpy does not compile with PY_ARRAY_TYPES_PREFIX
by Sasha 27 Jan '06

27 Jan '06

On 1/27/06, Travis Oliphant <oliphant(a)ee.byu.edu> wrote: > Show an example of using it in a file before you include the numpy > header. Because that *should* work. I know, I just tested it a few > days ago... I've tried to put just two lines in "test.c": #define PY_ARRAY_TYPES_PREFIX XYZ_ #include <numpy/arrayobject.h> and compile it with $ gcc -I$NUMPYINCLUDE -c test.c Where NUMPYINCLUDE points to the location of numpy/arrayobject.h I get the following errors: In file included from test.c:2: numpy-0.9.4/lib/python2.3/site-packages/numpy/core/include/numpy/arrayobject.h:699: error: syntax error before " XYZ_intp" numpy-0.9.4/lib/python2.3/site-packages/numpy/core/include/numpy/arrayobject.h:699: warning: data definition has no type or storage class numpy-0.9.4/lib/python2.3/site-packages/numpy/core/include/numpy/arrayobject.h:700: error: syntax error before " XYZ_uintp" ... <many screenfulls more> ...

4 8

UnsignedInt32
by Sasha 27 Jan '06

27 Jan '06

Numeric has both UInt32 and UnsignedInt32 defined, but Numpy only has UInt32. Is it intentional or an oversight? Thanks.

2 2

Fwd: [Numpy-discussion] Numpy does not compile with PY_ARRAY_TYPES_PREFIX
by Sasha 27 Jan '06

27 Jan '06

Numpy-discussion list rejected an attachment. Here are a few relevant lines from the log: In file included from numpy/core/src/multiarraymodule.c:65: numpy/core/src/arrayobject.c: In function `PyArray_FromDimsAndDataAndDescr': numpy/core/src/arrayobject.c:766: `intp' undeclared (first use in this function) numpy/core/src/arrayobject.c:766: parse error before ')' token In file included from numpy/core/src/multiarraymodule.c:65: numpy/core/src/arrayobject.c: At top level: numpy/core/src/arrayobject.c:822: parse error before "intp" numpy/core/src/arrayobject.c:822: warning: function declaration isn't a prototype numpy/core/src/arrayobject.c: In function `PyArray_Scalar': numpy/core/src/arrayobject.c:841: `Bool' undeclared (first use in this function) numpy/core/src/arrayobject.c:841: parse error before ')' token numpy/core/src/arrayobject.c:841: parse error before ')' token numpy/core/src/arrayobject.c:841: warning: left-hand operand of comma expression has no effect ---------- Forwarded message ---------- From: Sasha <ndarray(a)mac.com> Date: Jan 27, 2006 12:33 PM Subject: Re: [Numpy-discussion] Numpy does not compile with PY_ARRAY_TYPES_PREFIX To: Andrew Straw <strawman(a)astraw.com>, numpy-discussion <numpy-discussion(a)lists.sourceforge.net> I've just updated to svn r2006. Regular build works fine, but $ CFLAGS=-DPY_ARRAY_TYPES_PREFIX=PyArray_NS_ python setup.py build produced the attached log. Note that I am not compiling any extention, just regular numpy. On 1/27/06, Andrew Straw <strawman(a)astraw.com> wrote: > Sasha wrote: > > >I have attempted to compile RPy (see http://rpy.sourceforge.net/) with > >numpy and found that both R and numpy headers define Int32: > > > >.../numpy/core/include/numpy/arrayobject.h:304: conflicting types for `Int32' > >.../lib/R/include/R_ext/Random.h:57: previous declaration of `Int32' > > > >I have tried to fix the problem by setting PY_ARRAY_TYPES_PREFIX as follows: > > > >$ CFLAGS=-DPY_ARRAY_TYPES_PREFIX=PyArray_NS_ python setup.py build > > > >This resulted in compile error in almost every Numpy source file. > > > >Am I using PY_ARRAY_TYPES_PREFIX correctly? If not, what is the > >recommended way to solve name conflicts involving Numpy typoes? > > > > > > David Cooke informed me some time ago that the #include > "numpy/arrayobject.h" line should go _after_ the other #includes. It's > worked for me well enough ever since, although it seems rather fragile. > Otherwise I'm not having the same issue with current svn. There was an > issue with release 0.9.4 for C++ code, anyway. > > Cheers! > Andrew > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Numpy-discussion mailing list > Numpy-discussion(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/numpy-discussion >

1 0

Fwd: [Numpy-discussion] Numpy does not compile with PY_ARRAY_TYPES_PREFIX
by Alexander Belopolsky 27 Jan '06

27 Jan '06

Numpy-discussion list rejected an attachment. Here are a few relevant lines from the log: In file included from numpy/core/src/multiarraymodule.c:65: numpy/core/src/arrayobject.c: In function `PyArray_FromDimsAndDataAndDescr': numpy/core/src/arrayobject.c:766: `intp' undeclared (first use in this function) numpy/core/src/arrayobject.c:766: parse error before ')' token In file included from numpy/core/src/multiarraymodule.c:65: numpy/core/src/arrayobject.c: At top level: numpy/core/src/arrayobject.c:822: parse error before "intp" numpy/core/src/arrayobject.c:822: warning: function declaration isn't a prototype numpy/core/src/arrayobject.c: In function `PyArray_Scalar': numpy/core/src/arrayobject.c:841: `Bool' undeclared (first use in this function) numpy/core/src/arrayobject.c:841: parse error before ')' token numpy/core/src/arrayobject.c:841: parse error before ')' token numpy/core/src/arrayobject.c:841: warning: left-hand operand of comma expression has no effect ---------- Forwarded message ---------- From: Sasha <ndarray(a)mac.com> Date: Jan 27, 2006 12:33 PM Subject: Re: [Numpy-discussion] Numpy does not compile with PY_ARRAY_TYPES_PREFIX To: Andrew Straw <strawman(a)astraw.com>, numpy-discussion <numpy-discussion(a)lists.sourceforge.net> I've just updated to svn r2006. Regular build works fine, but $ CFLAGS=-DPY_ARRAY_TYPES_PREFIX=PyArray_NS_ python setup.py build produced the attached log. Note that I am not compiling any extention, just regular numpy. On 1/27/06, Andrew Straw <strawman(a)astraw.com> wrote: > Sasha wrote: > > >I have attempted to compile RPy (see http://rpy.sourceforge.net/) with > >numpy and found that both R and numpy headers define Int32: > > > >.../numpy/core/include/numpy/arrayobject.h:304: conflicting types for `Int32' > >.../lib/R/include/R_ext/Random.h:57: previous declaration of `Int32' > > > >I have tried to fix the problem by setting PY_ARRAY_TYPES_PREFIX as follows: > > > >$ CFLAGS=-DPY_ARRAY_TYPES_PREFIX=PyArray_NS_ python setup.py build > > > >This resulted in compile error in almost every Numpy source file. > > > >Am I using PY_ARRAY_TYPES_PREFIX correctly? If not, what is the > >recommended way to solve name conflicts involving Numpy typoes? > > > > > > David Cooke informed me some time ago that the #include > "numpy/arrayobject.h" line should go _after_ the other #includes. It's > worked for me well enough ever since, although it seems rather fragile. > Otherwise I'm not having the same issue with current svn. There was an > issue with release 0.9.4 for C++ code, anyway. > > Cheers! > Andrew > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Numpy-discussion mailing list > Numpy-discussion(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/numpy-discussion >

1 0

Numpy does not compile with PY_ARRAY_TYPES_PREFIX
by Sasha 27 Jan '06

27 Jan '06

I have attempted to compile RPy (see http://rpy.sourceforge.net/) with numpy and found that both R and numpy headers define Int32: .../numpy/core/include/numpy/arrayobject.h:304: conflicting types for `Int32' .../lib/R/include/R_ext/Random.h:57: previous declaration of `Int32' I have tried to fix the problem by setting PY_ARRAY_TYPES_PREFIX as follows: $ CFLAGS=-DPY_ARRAY_TYPES_PREFIX=PyArray_NS_ python setup.py build This resulted in compile error in almost every Numpy source file. Am I using PY_ARRAY_TYPES_PREFIX correctly? If not, what is the recommended way to solve name conflicts involving Numpy typoes? Thanks.

2 1