Re: [Numpy-discussion] Fixing issue of future opaqueness of ndarray this summer

2012-05-12 Thread Travis Oliphant
On May 12, 2012, at 9:39 PM, Matthew Brett wrote: > Hi, > > On Sat, May 12, 2012 at 7:24 PM, Travis Oliphant wrote: >> >> On May 12, 2012, at 9:01 PM, Matthew Brett wrote: >> >>> Hi, >>> >>> On Sat, May 12, 2012 at 5:30 PM, Travis Oliphant >>> wrote: Your thoughts are definitely the f

Re: [Numpy-discussion] Should arr.diagonal() return a copy or a view? (1.7 compatibility issue)

2012-05-12 Thread Benjamin Root
On Saturday, May 12, 2012, Travis Oliphant wrote: > Another approach would be to introduce a method: > > a.diag(copy=False) > > and leave a.diagonal() alone. Then, a.diagonal() could be deprecated over > 2-3 releases. > > -Travis > +1 Ben Root > ___

Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1

2012-05-12 Thread Orion Poplawski
On 05/05/2012 12:15 PM, Ralf Gommers wrote: > Hi, > > I'm pleased to announce the availability of the first release candidate > of NumPy 1.6.2. This is a maintenance release. Due to the delay of the > NumPy 1.7.0, this release contains far more fixes than a regular NumPy > bugfix release. It also

Re: [Numpy-discussion] Fixing issue of future opaqueness of ndarray this summer

2012-05-12 Thread Matthew Brett
Hi, On Sat, May 12, 2012 at 7:24 PM, Travis Oliphant wrote: > > On May 12, 2012, at 9:01 PM, Matthew Brett wrote: > >> Hi, >> >> On Sat, May 12, 2012 at 5:30 PM, Travis Oliphant wrote: >>> Your thoughts are definitely the future.   We are currently building such a >>> thing.   We would like it

Re: [Numpy-discussion] Should arr.diagonal() return a copy or a view? (1.7 compatibility issue)

2012-05-12 Thread Travis Oliphant
Another approach would be to introduce a method: a.diag(copy=False) and leave a.diagonal() alone. Then, a.diagonal() could be deprecated over 2-3 releases. -Travis On May 12, 2012, at 8:31 AM, Ralf Gommers wrote: > > > On Sat, May 12, 2012 at 1:54 AM, Nathaniel Smith wrote: > On Fri, M

Re: [Numpy-discussion] Fixing issue of future opaqueness of ndarray this summer

2012-05-12 Thread Travis Oliphant
On May 12, 2012, at 9:01 PM, Matthew Brett wrote: > Hi, > > On Sat, May 12, 2012 at 5:30 PM, Travis Oliphant wrote: >> Your thoughts are definitely the future. We are currently building such a >> thing. We would like it to be open source.We are currently preparing a >> proposal to DAR

Re: [Numpy-discussion] Fixing issue of future opaqueness of ndarray this summer

2012-05-12 Thread Matthew Brett
Hi, On Sat, May 12, 2012 at 5:30 PM, Travis Oliphant wrote: > Your thoughts are definitely the future.   We are currently building such a > thing.   We would like it to be open source.    We are currently preparing a > proposal to DARPA as part of their XDATA proposal in order to help fund this

Re: [Numpy-discussion] Fixing issue of future opaqueness of ndarray this summer

2012-05-12 Thread Travis Oliphant
> > I think the long-term generality is a lot bigger than that: > > - Compressed arrays > - Interfaces to HDF files > - Distributed-memory arrays > - Blocked arrays > - Semi-sparse and sparse (diagonal, but also triangular, symmetric, > repeating, ...) > - Lazy evaluation: "generating_mult

Re: [Numpy-discussion] Fixing issue of future opaqueness of ndarray this summer

2012-05-12 Thread Charles R Harris
On Sat, May 12, 2012 at 3:55 PM, Dag Sverre Seljebotn < d.s.seljeb...@astro.uio.no> wrote: > On 05/11/2012 03:37 PM, mark florisson wrote: > > On 11 May 2012 12:13, Dag Sverre Seljebotn > wrote: > >> (NumPy devs: I know, I get too many ideas. But this time I *really* > believe > >> in it, I think

Re: [Numpy-discussion] Fixing issue of future opaqueness of ndarray this summer

2012-05-12 Thread Dag Sverre Seljebotn
On 05/11/2012 03:37 PM, mark florisson wrote: > On 11 May 2012 12:13, Dag Sverre Seljebotn wrote: >> (NumPy devs: I know, I get too many ideas. But this time I *really* believe >> in it, I think this is going to be *huge*. And if Mark F. likes it it's not >> going to be without manpower; and as hi

Re: [Numpy-discussion] Fixing issue of future opaqueness of ndarray this summer

2012-05-12 Thread Dag Sverre Seljebotn
On 05/12/2012 11:35 PM, Dag Sverre Seljebotn wrote: > On 05/11/2012 03:25 PM, mark florisson wrote: >> On 11 May 2012 12:13, Dag Sverre Seljebotn >> wrote: >>> (NumPy devs: I know, I get too many ideas. But this time I *really* believe >>> in it, I think this is going to be *huge*. And if Mark F

Re: [Numpy-discussion] Fixing issue of future opaqueness of ndarray this summer

2012-05-12 Thread Dag Sverre Seljebotn
On 05/11/2012 03:25 PM, mark florisson wrote: > On 11 May 2012 12:13, Dag Sverre Seljebotn wrote: >> (NumPy devs: I know, I get too many ideas. But this time I *really* believe >> in it, I think this is going to be *huge*. And if Mark F. likes it it's not >> going to be without manpower; and as hi

Re: [Numpy-discussion] Fixing issue of future opaqueness of ndarray this summer

2012-05-12 Thread Dag Sverre Seljebotn
On 05/11/2012 10:10 PM, Mark Wiebe wrote: > On Fri, May 11, 2012 at 6:13 AM, Dag Sverre Seljebotn > mailto:d.s.seljeb...@astro.uio.no>> wrote: > > (NumPy devs: I know, I get too many ideas. But this time I *really* > believe in it, I think this is going to be *huge*. And if Mark F. likes >

Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1

2012-05-12 Thread Ralf Gommers
On Sun, May 6, 2012 at 12:12 AM, Charles R Harris wrote: > > > On Sat, May 5, 2012 at 2:56 PM, Paul Anton Letnes < > paul.anton.let...@gmail.com> wrote: > >> Hi, >> >> I'm getting a couple of errors when testing. System: >> Arch Linux (updated today) >> Python 3.2.3 >> gcc 4.7.0 >> (Anything else

Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1

2012-05-12 Thread Ralf Gommers
On Sat, May 12, 2012 at 6:22 PM, Sandro Tosi wrote: > Hello, > > On Sat, May 5, 2012 at 8:15 PM, Ralf Gommers > wrote: > > Hi, > > > > I'm pleased to announce the availability of the first release candidate > of > > NumPy 1.6.2. This is a maintenance release. Due to the delay of the > NumPy > >

Re: [Numpy-discussion] Problems when using ACML with numpy

2012-05-12 Thread Thomas Unterthiner
On 05/12/2012 05:34 PM, Pauli Virtanen wrote: > 12.05.2012 17:30, Thomas Unterthiner kirjoitti: > [clip] >> However it didn't seem to work. The same 5000x5000 matrix-multiply is >> still spinning at 100% CPU usage. I attached to the process after I let >> it run for over 3 minutes, and the stacktra

Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1

2012-05-12 Thread Sandro Tosi
Hello, On Sat, May 5, 2012 at 8:15 PM, Ralf Gommers wrote: > Hi, > > I'm pleased to announce the availability of the first release candidate of > NumPy 1.6.2.  This is a maintenance release. Due to the delay of the NumPy > 1.7.0, this release contains far more fixes than a regular NumPy bugfix >

Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1

2012-05-12 Thread Ralf Gommers
On Sat, May 5, 2012 at 11:06 PM, Charles R Harris wrote: > > > On Sat, May 5, 2012 at 2:56 PM, Paul Anton Letnes < > paul.anton.let...@gmail.com> wrote: > >> Hi, >> >> I'm getting a couple of errors when testing. System: >> Arch Linux (updated today) >> Python 3.2.3 >> gcc 4.7.0 >> (Anything else

Re: [Numpy-discussion] ANN: NumPy 1.6.2 release candidate 1

2012-05-12 Thread Ralf Gommers
On Tue, May 8, 2012 at 3:23 PM, Derek Homeier < de...@astro.physik.uni-goettingen.de> wrote: > On 06.05.2012, at 8:16AM, Paul Anton Letnes wrote: > > > All tests for 1.6.2rc1 pass on > > Mac OS X 10.7.3 > > python 2.7.2 > > gcc 4.2 (Apple) > > Passing as well on 10.6 x86_64 and on 10.5.8 ppc with

Re: [Numpy-discussion] Problems when using ACML with numpy

2012-05-12 Thread Pauli Virtanen
12.05.2012 17:30, Thomas Unterthiner kirjoitti: [clip] > However it didn't seem to work. The same 5000x5000 matrix-multiply is > still spinning at 100% CPU usage. I attached to the process after I let > it run for over 3 minutes, and the stacktrace looked like this: > > #0 DOUBLE_dot (ip1=, is1=8

Re: [Numpy-discussion] Problems when using ACML with numpy

2012-05-12 Thread Thomas Unterthiner
On 05/12/2012 04:00 PM, Matthieu Brucher wrote: Does ACML now provide a CBLAS interface? Matthieu D'oh! Very good point, I wasn't aware that numpy needed a CLBAS interface. I now followed the steps outlined at the end of http://mail.scipy.org/pipermail/numpy-discussion/2006-February/018379

Re: [Numpy-discussion] Problems when using ACML with numpy

2012-05-12 Thread Matthieu Brucher
Does ACML now provide a CBLAS interface? Matthieu 2012/5/12 Thomas Unterthiner > > On 05/12/2012 03:27 PM, numpy-discussion-requ...@scipy.org wrote: > > 12.05.2012 00:54, Thomas Unterthiner kirjoitti: > > [clip] > >> > The process will have 100% CPU usage and will not show any activity > >> >

Re: [Numpy-discussion] Problems when using ACML with numpy

2012-05-12 Thread Thomas Unterthiner
On 05/12/2012 03:27 PM, numpy-discussion-requ...@scipy.org wrote: > 12.05.2012 00:54, Thomas Unterthiner kirjoitti: > [clip] >> > The process will have 100% CPU usage and will not show any activity >> > under strace. A gdb backtrace looks as follows: >> > >> > (gdb) bt >> > #0 0x7fdcc00

Re: [Numpy-discussion] Should arr.diagonal() return a copy or a view? (1.7 compatibility issue)

2012-05-12 Thread Ralf Gommers
On Sat, May 12, 2012 at 1:54 AM, Nathaniel Smith wrote: > On Fri, May 11, 2012 at 9:26 PM, T J wrote: > > On Fri, May 11, 2012 at 1:12 PM, Mark Wiebe wrote: > >> > >> On Fri, May 11, 2012 at 2:18 PM, Pauli Virtanen wrote: > >>> > >>> 11.05.2012 17:54, Frédéric Bastien kirjoitti: > >>> > In The

Re: [Numpy-discussion] Problems when using ACML with numpy

2012-05-12 Thread Pauli Virtanen
12.05.2012 00:54, Thomas Unterthiner kirjoitti: [clip] > The process will have 100% CPU usage and will not show any activity > under strace. A gdb backtrace looks as follows: > > (gdb) bt > #0 0x7fdcc000e524 in ?? () > from /usr/lib/python2.7/dist-packages/numpy/core/multiarray.so [clip]

Re: [Numpy-discussion] Issue with numpy.random.multivariate_normal Linux RHEL4 np version: 1.6.1

2012-05-12 Thread John Gleeson
On 2012-05-11, at 4:01 PM, Norman Shelley wrote: > Running on Linux RHEL4 > > numpy.random.multivariate_normal seems to work well for 25 mean > values but when I go to 26 mean values (and their corresponding > covariance values) it produces garbage. > Any ideas? The implementation of multiv