[Numpy-discussion] Python equivalent of bwboundaries, bwlabel

2007-06-28 Thread Cameron Walsh
Hi all, I'm trying to do object segmentation from image slices, and have found the matlab functions bwlabel and bwboundaries. I haven't been able to find a python equivalent in the pylab, scipy, numpy, or Image modules, nor has google been fruitful. Could somebody point me in the right directio

Re: [Numpy-discussion] [ANN]New numpy, scipy and atlas rpms for FC 5, 6 and 7 and openSUSE (with 64 bits arch support)

2007-06-28 Thread David Cournapeau
Eike Welk wrote: > On Sunday 24 June 2007 13:05, David Cournapeau wrote: >> Hi there, >> >> After quite some pain, I finally managed to build a LAPACK + >> ATLAS rpm useful for numpy and scipy. Read the following if you > > --- snip -- > >> a

[Numpy-discussion] baffled by gfortran

2007-06-28 Thread Mathew Yeates
I have gfortran installed in my path. But when I run python setup.py build I get Found executable /usr/bin/g77 gnu: no Fortran 90 compiler found gnu: no Fortran 90 compiler found customize GnuFCompiler gnu: no Fortran 90 compiler found gnu: no Fortran 90 compiler found The output of python setup.

Re: [Numpy-discussion] How is NumPy implemented?

2007-06-28 Thread Geoffrey Zhu
I see. Thanks a lot. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Denniston Sent: Thursday, June 28, 2007 3:33 PM To: Discussion of Numerical Python Subject: Re: [Numpy-discussion] How is NumPy implemented? That is normal python syntax. It works

Re: [Numpy-discussion] Unhandled floating point exception running test in numpy-1.0.3 and svn 3875

2007-06-28 Thread Andrew Straw
john, there was a bug that made it into debian sarge whereby a SIGFPE wasn't trapped in the appropriate place and ended up causing problems similar to what you describe. the difficulty in debugging is that you're after whatever triggers the FPE in the first place (or the bug that lets it go untrap

Re: [Numpy-discussion] How is NumPy implemented?

2007-06-28 Thread Tom Denniston
That is normal python syntax. It works with lists. What is slightly unusual is the multi-dimensional slicing as in arr[:,10:20]. However, this is governed by the way python translates bracket[] index calls to the __getitem__ and __getslice__ methods. You can try it out yourself in ipython or yo

Re: [Numpy-discussion] How is NumPy implemented?

2007-06-28 Thread Fernando Perez
On 6/28/07, Geoffrey Zhu <[EMAIL PROTECTED]> wrote: > Hi All, > > I am curious how numpy is implemented. Syntax such as x[10::-2] is > completely foreign to Python. How does numpy get Python to support it? Completely foreign to Python? In [1]: x="Geoffrey Zhu" In [2]: x[10::-2] Out[2]: 'h efoG'

Re: [Numpy-discussion] How is NumPy implemented?

2007-06-28 Thread Matthieu Brucher
2007/6/28, Geoffrey Zhu <[EMAIL PROTECTED]>: Hi All, I am curious how numpy is implemented. Syntax such as x[10::-2] is completely foreign to Python. This syntax is supported by Python, it is a slice, and it is the same syntax for lists. Matthieu

Re: [Numpy-discussion] [ANN]New numpy, scipy and atlas rpms for FC 5, 6 and 7 and openSUSE (with 64 bits arch support)

2007-06-28 Thread Eike Welk
On Sunday 24 June 2007 13:05, David Cournapeau wrote: > Hi there, > > After quite some pain, I finally managed to build a LAPACK + > ATLAS rpm useful for numpy and scipy. Read the following if you --- snip -- > and lapack. I would like to h

[Numpy-discussion] How is NumPy implemented?

2007-06-28 Thread Geoffrey Zhu
Hi All, I am curious how numpy is implemented. Syntax such as x[10::-2] is completely foreign to Python. How does numpy get Python to support it? Thanks, Geoffrey PS. Ignore the disclaimer. The mail server automatically insert that. ___=0A= =0

Re: [Numpy-discussion] Unhandled floating point exception running test in numpy-1.0.3 and svn 3875

2007-06-28 Thread John Ollinger
rex nosyntax.com> writes: > > > There doesn't appear to be a problem with recent versions of the > software. In particular, ATLAS 3.7.33 does not cause an error. > > Is there some reason for you to use such old software? (gcc 3.3.1 & > kernel 2.4.21)? What platform are you building for? > >

[Numpy-discussion] segfault caused by incorrect Py_DECREF in ufunc

2007-06-28 Thread Tom Denniston
Below is the code around line 900 for ufuncobject.c (http://svn.scipy.org/svn/numpy/trunk/numpy/core/src/ufuncobject.c) There is a decref labeled with ">>>" below that is incorrect. As per the python documentation (http://docs.python.org/api/dictObjects.html): #PyObject* PyDict_GetItem( PyObject