Re: [Numpy-discussion] Sphinx/Numpydoc, attributes and property

2009-10-22 Thread Fabricio Silva
It seems that class Profil(object): def __init__(self): """ """ pass def bla(self): "Blabla." return 0 @property def tdeb(self): "The time horizon startpoint." return self.pts[0,:].min() > and a foo.rst conta

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Sturla Molden
Robert Kern skrev: > I would be delighted to see a reference to one that refers to a high > level language's API as SIMD. Please point one out to me. It's > certainly not any of the ones I have available to me. > > Numerical Receipes in Fortran 90, page 964 and 985-986, describes the syntax of

[Numpy-discussion] Sphinx/Numpydoc, attributes and property

2009-10-22 Thread Fabricio Silva
It seems that either Sphinx or NumpyDoc is having troubles with property attributes. Considering the following piece of code in foo.py class Profil(object): """ Blabla Attributes -- tfin tdeb : flo

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Robert Kern
On Thu, Oct 22, 2009 at 06:20, Dag Sverre Seljebotn wrote: > Robert Kern wrote: >> On Wed, Oct 21, 2009 at 22:32, Mathieu Blondel wrote: >> >>> On Thu, Oct 22, 2009 at 11:31 AM, Sturla Molden wrote: >>> Mathieu Blondel skrev: > Hello, > > About one year ago, a high-level, o

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Robert Kern
On Thu, Oct 22, 2009 at 02:35, Sturla Molden wrote: > Robert Kern skrev: >> No, I think you're right. Using "SIMD" to refer to numpy-like >> operations is an abuse of the term not supported by any outside >> community that I am aware of. Everyone else uses "SIMD" to describe >> hardware instructio

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Robert Ferrell
On Oct 22, 2009, at 1:35 AM, Sturla Molden wrote: > Robert Kern skrev: >> No, I think you're right. Using "SIMD" to refer to numpy-like >> operations is an abuse of the term not supported by any outside >> community that I am aware of. Everyone else uses "SIMD" to describe >> hardware instruction

[Numpy-discussion] Antwort: Re: why does binary_repr don't support arrays

2009-10-22 Thread markus . proeller
numpy-discussion-boun...@scipy.org schrieb am 22.10.2009 12:36:46: > > > > > > On Tue, Oct 20, 2009 at 11:17 AM, wrote: > > > > Hello, > > > > I'm always wondering why binary_repr doesn't allow arrays as input > > values. I always have to use a work around like: > > > > import numpy as np

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Dag Sverre Seljebotn
Robert Kern wrote: > On Wed, Oct 21, 2009 at 22:32, Mathieu Blondel wrote: > >> On Thu, Oct 22, 2009 at 11:31 AM, Sturla Molden wrote: >> >>> Mathieu Blondel skrev: >>> Hello, About one year ago, a high-level, objected-oriented SIMD API was added to Mono. For ex

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Gregor Thalhammer
2009/10/21 Neal Becker > ... > > I once wrote a module that replaces the built in transcendental > > functions of numpy by optimized versions from Intels vector math > > library. If someone is interested, I can publish it. In my experience it > > was of little use since real world problems are li

Re: [Numpy-discussion] why does binary_repr don't support arrays

2009-10-22 Thread Ralf Gommers
On Tue, Oct 20, 2009 at 11:17 AM, wrote: > > Hello, > > I'm always wondering why binary_repr doesn't allow arrays as input values. > I always have to use a work around like: > > import numpy as np > > def binary_repr(arr, width=None): > binary_list = map((lambda foo: np.binary_repr(foo, width

Re: [Numpy-discussion] Optimized sum of squares

2009-10-22 Thread Gary Ruben
josef.p...@gmail.com wrote: > Is it really possible to get the same as np.sum(a*a, axis) with > tensordot if a.ndim=2 ? > Any way I try the "something_else", I get extra terms as in np.dot(a.T, a) Just to answer this question, np.dot(a,a) is equivalent to np.tensordot(a,a, axis=(0,0)) but the l

[Numpy-discussion] ANN: SciPy October Sprint

2009-10-22 Thread Stéfan van der Walt
Hi all, The weekend is just around the corner, and we're looking forward to the sprint!  Here is the detail again: """ Our patch queue keeps getting longer and longer, so here is an opportunity to do some spring cleaning (it's spring in South Africa, at least)! Please join us for an October SciP

[Numpy-discussion] Convolution of a masked array

2009-10-22 Thread Nadav Horesh
Is there a way to proper convolve a masked array with a normal (nonmasked) array? My specific problem is a convolution of a 2D masked array with a separable kernel (a convolution with 2 1D array along each axis). Nadav. ___ NumPy-Discussion mail

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Sturla Molden
Mathieu Blondel skrev: > As I wrote earlier in this thread, I confused Cython and CPython. PN > was suggesting to include Numpy in the CPython distribution (not > Cython). The reason why was also given earlier. > > First, that would currently not be possible, as NumPy does not support Py3k. Se

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Mathieu Blondel
On Thu, Oct 22, 2009 at 5:05 PM, Sturla Molden wrote: > Mathieu Blondel skrev: > The PEP 3118 buffer syntax in Cython can be used to port NumPy to Py3k, > replacing the current C source. That might be what Norvig meant if he > suggested merging NumPy into Cython. As I wrote earlier in this threa

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Sturla Molden
Mathieu Blondel skrev: > Peter Norvig suggested to merge Numpy into Cython but he didn't > mention SIMD as the reason (this one is from me). I don't know what Norvig said or meant. However: There is NumPy support in Cython. Cython has a general syntax applicable to any PEP 3118 buffer. (As Num

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Sturla Molden
Matthieu Brucher skrev: > I agree with Sturla, for instance nVidia GPUs do SIMD computations > with blocs of 16 values at a time, but the hardware behind can't > compute on so much data at a time. It's SIMD from our point of view, > just like Numpy does ;) > > A computer with a CPU and a GPU is

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Matthieu Brucher
>> OK, I should have said "Object-oriented SIMD API that is implemented >> using hardware SIMD instructions". > > No, I think you're right. Using "SIMD" to refer to numpy-like > operations is an abuse of the term not supported by any outside > community that I am aware of. Everyone else uses "SIMD"

Re: [Numpy-discussion] Objected-oriented SIMD API for Numpy

2009-10-22 Thread Sturla Molden
Robert Kern skrev: > No, I think you're right. Using "SIMD" to refer to numpy-like > operations is an abuse of the term not supported by any outside > community that I am aware of. Everyone else uses "SIMD" to describe > hardware instructions, not the application of a single syntactical > element o

Re: [Numpy-discussion] Using numpydoc outside of numpy

2009-10-22 Thread David Warde-Farley
On Wed, Oct 21, 2009 at 11:13:35AM -0400, Michael Droettboom wrote: > Sorry for the noise. Found the instructions in HOWTO_BUILD_DOCS.txt . Not sure if this is part of what you discovered, but numpydoc is at the Cheese Shop too: http://pypi.python.org/pypi/numpydoc David __