Re: [Numpy-discussion] array of matrices

On Sat, Mar 28, 2009 at 23:15, Anne Archibald wrote: > 2009/3/28 Geoffrey Irving : >> On Sat, Mar 28, 2009 at 12:47 AM, Robert Kern wrote: >>> 2009/3/27 Charles R Harris : On Fri, Mar 27, 2009 at 4:43 PM, Robert Kern wrote: > > On Fri, Mar 27, 2009 at 17:38, Bryan Cole wrote:

Re: [Numpy-discussion] array of matrices

2009/3/28 Geoffrey Irving : > On Sat, Mar 28, 2009 at 12:47 AM, Robert Kern wrote: >> 2009/3/27 Charles R Harris : >>> >>> On Fri, Mar 27, 2009 at 4:43 PM, Robert Kern wrote: On Fri, Mar 27, 2009 at 17:38, Bryan Cole wrote: > I have a number of arrays of shape (N,4,4). I need to p

Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

On 3/28/2009 9:26 AM David Cournapeau apparently wrote: > I am pleased to announce the release of the rc1 for numpy > 1.3.0. You can find source tarballs and installers for both Mac OS X > and Windows on the sourceforge page: > https://sourceforge.net/projects/numpy/ Was the Python 2.6 Superpack i

Re: [Numpy-discussion] Failure with 1.3.0b1 under Solaris 10 SPARC

On Sat, Mar 28, 2009 at 6:35 PM, Charles R Harris wrote: > > > On Sat, Mar 28, 2009 at 5:31 PM, Jeff Blaine wrote: > >> Same problem with 1.3.0rc1 >> >> Jeff Blaine wrote: >> > Aside from this, the website for NumPy should have a link to the >> > list subscription address, not a link to the list

Re: [Numpy-discussion] Failure with 1.3.0b1 under Solaris 10 SPARC

On Sat, Mar 28, 2009 at 5:31 PM, Jeff Blaine wrote: > Same problem with 1.3.0rc1 > > Jeff Blaine wrote: > > Aside from this, the website for NumPy should have a link to the > > list subscription address, not a link to the list itself (which > > cannot be posted to unless one is a member). > > > >

Re: [Numpy-discussion] Failure with 1.3.0b1 under Solaris 10 SPARC

Same problem with 1.3.0rc1 Jeff Blaine wrote: > Aside from this, the website for NumPy should have a link to the > list subscription address, not a link to the list itself (which > cannot be posted to unless one is a member). > > Python 2.4.2 (#2, Dec 6 2006, 17:18:19) > [GCC 3.3.5] on sunos5 >

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

just to see if it would work. I compiled against the .so's and just didnt worry about the linking error. Then i installed numpy and ran numpy.test() these are the results: Ran 2030 tests in 9.778s OK (KNOWNFAIL=1, SKIP=11) so i guess that means its ok.. Chris On Sat, Mar 28, 2009 at 6:30 P

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

aside from a smaller numpy install size, what do i gain from linking against the .so's vs the static libraries? Chris On Sat, Mar 28, 2009 at 6:09 PM, Chris Colbert wrote: > what does ldconfig do other than refresh the library path? > > i copied the .so's to /usr/local/atlas/lib and added that

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

what does ldconfig do other than refresh the library path? i copied the .so's to /usr/local/atlas/lib and added that path to /etc/ld.so.conf.d/scipy.conf and then did ldconfig this was before building numpy Chris 2009/3/28 Charles R Harris > > > On Sat, Mar 28, 2009 at 3:34 PM, Charles R Har

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

On Sat, Mar 28, 2009 at 3:34 PM, Charles R Harris wrote: > > > 2009/3/28 Chris Colbert > >> YES! YES! YES! YES! HAHAHAHA! YES! >> >> using these flags in make.inc to build lapack 1.3.1 worked: >> >> OPTS = O2 -fPIC -m32 >> NOPTS = O2 -fPIC -m32 >> >> then build atlas as normal and build numpy ag

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

2009/3/28 Chris Colbert > YES! YES! YES! YES! HAHAHAHA! YES! > > using these flags in make.inc to build lapack 1.3.1 worked: > > OPTS = O2 -fPIC -m32 > NOPTS = O2 -fPIC -m32 > > then build atlas as normal and build numpy against the static atlas > libraries (building against the .so's created by

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

YES! YES! YES! YES! HAHAHAHA! YES! using these flags in make.inc to build lapack 1.3.1 worked: OPTS = O2 -fPIC -m32 NOPTS = O2 -fPIC -m32 then build atlas as normal and build numpy against the static atlas libraries (building against the .so's created by atlas causes a linking error in numpy bui

Re: [Numpy-discussion] Is it ok to include GPL scripts in the numpy *repository* ?

Alan G Isaac wrote: > On 3/27/2009 6:48 AM David Cournapeau apparently wrote: >> To build the numpy .dmg mac os x installer, I use a script from the >> adium project, which uses applescript and some mac os x black magic. The >> script seems to be GPL, as adium itself: > > > It might be worth

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

yeah, I set -b 32 on atlas... the bogus atlas config was telling me to set OPTS = O -fPIC -m32 and NOPTS = O -fPIC -m32, this caused the make process of lapack to hang. So i set OPTS = O2 -fPIC -m32 and NOPTS = O0 -fPIC -m32. Which is the same as all of my first attempts except for the presence

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

2009/3/28 Chris Colbert > i just ran a dummy config on atlas and its giving me different OPTS and > NOOPTS flags than the scipy tutorial. so im gonna try that and report back > I think that I also had to explicitly specify the bit size flag on the ATLAS command line during various builds, -b32/6

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

i just ran a dummy config on atlas and its giving me different OPTS and NOOPTS flags than the scipy tutorial. so im gonna try that and report back Chris 2009/3/28 Charles R Harris > > > 2009/3/28 Chris Colbert > >> I notice my OPTS and NOOPTS are different than yours. (I went of >> scipy.org i

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

2009/3/28 Chris Colbert > I notice my OPTS and NOOPTS are different than yours. (I went of > scipy.orginstall guide) > > Do you think that's the issue? > Probably not, but my experience is limited. IIRC, I also had to get the command line for building ATLAS just right and build LAPACK separatel

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

I notice my OPTS and NOOPTS are different than yours. (I went of scipy.orginstall guide) Do you think that's the issue? Cheers, Chris ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

here it is: 32 bit Intrepid # LAPACK make include file. # # LAPACK, Version 3.1.1 # # February 2007

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

2009/3/28 Chris Colbert > this is really, really, half of numpy.linalg works, the other half doesn't. > > > working functions: > > cholesky > det > inv > norm > solve > > non-working functions (they all hang at 100% cpu): > > eig > eigh > eigvals > eigvalsh > pinv > lstsq > svd > > > > I must be

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

this is really, really, half of numpy.linalg works, the other half doesn't. working functions: cholesky det inv norm solve non-working functions (they all hang at 100% cpu): eig eigh eigvals eigvalsh pinv lstsq svd I must be a total n00b to be the only person running into this problem :) Ch

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

Robin, Thanks. I need to get the backport for multiprocessing on 2.5. But now, it's more of a matter of not wanting to admit defeat Cheers, Chris On Sat, Mar 28, 2009 at 2:30 PM, Robin wrote: > 2009/3/28 Chris Colbert : > > Alright, building numpy against atlas from the repositories work

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

2009/3/28 Chris Colbert : > Alright, building numpy against atlas from the repositories works, but this > atlas only contains the single threaded libraries. So i would like to get my > build working completely. It doesn't help at all with your problem - but I thought I'd point out there are other

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

2009/3/29 Chris Colbert : > going back and looking at this error: > > C compiler: gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -fPIC > > compile options: '-c' > gcc: _configtest.c > gcc -pthread _configtest.o -L/usr/local/atlas/lib -llapack -lptf77blas > -lp

Re: [Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

going back and looking at this error: C compiler: gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC compile options: '-c' gcc: _configtest.c gcc -pthread _configtest.o -L/usr/local/atlas/lib -llapack -lptf77blas -lptcblas -latlas -o _configtest /usr/bin/ld:

Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

Hi David, On Mar 28, 2009, at 12:04 PM, David Cournapeau wrote: > Hi Robert, > > Thanks for the report. > > On Sun, Mar 29, 2009 at 12:10 AM, Robert Pyle > wrote: >> The Mac OS X installer (numpy-1.3.0rc1-py2.5-macosx10.5.dmg) did not >> work for me. It said none of my disks were suitable fo

Re: [Numpy-discussion] How to tell whether I am using 32 bitor64bit numpy?

David: The OS is 64-bit Windows Vista Home Premium, Service Pack 1 with 8gb ram. Machine is used as a desktop development machine (not a server). Dinesh From: David Cournapeau Sent: Saturday, March 28, 2009 9:11 AM To: Discussion of Numerical Python Subject: Re: [Numpy-discussion] How to t

Re: [Numpy-discussion] array of matrices

On Sat, Mar 28, 2009 at 12:47 AM, Robert Kern wrote: > 2009/3/27 Charles R Harris : >> >> On Fri, Mar 27, 2009 at 4:43 PM, Robert Kern wrote: >>> >>> On Fri, Mar 27, 2009 at 17:38, Bryan Cole wrote: >>> > I have a number of arrays of shape (N,4,4). I need to perform a >>> > vectorised matrix-mul

Re: [Numpy-discussion] How to tell whether I am using 32 bitor 64bit numpy?

2009/3/29 Dinesh B Vadhia : > David > > 1)  32-bit Numpy/Scipy with 32-bit Python on 64-bit Windows does work.  But, > it doesn't take advantage of memory > 2gb. Indeed. But running numpy 32 bits in python 64 bits is not possible - and even if it were, I guess it could not handle more than 32 bits

Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

Hi Robert, Thanks for the report. On Sun, Mar 29, 2009 at 12:10 AM, Robert Pyle wrote: > Hi all, > > On Mar 28, 2009, at 9:26 AM, David Cournapeau wrote: >> I am pleased to announce the release of the rc1 for numpy >> 1.3.0. You can find source tarballs and installers for both Mac OS X >> and Wi

Re: [Numpy-discussion] DVCS at PyCon

Hi Travis, On Sat, Mar 28, 2009 at 11:54 PM, Travis E. Oliphant wrote: > > FYI from PyCon > > Here at PyCon, it has been said that Python will be moving towards DVCS > and will be using bzr or mecurial, but explicitly *not* git.   It would > seem that *git* got the "lowest" score in the Developer

Re: [Numpy-discussion] How to tell whether I am using 32 bitor 64bit numpy?

David 1) 32-bit Numpy/Scipy with 32-bit Python on 64-bit Windows does work. But, it doesn't take advantage of memory > 2gb. 2) Happy to help out with the experimental 64-bit builds of Numpy/Scipy. But, would this be with pre-installed Windows libraries or source files as I'm not setup for

Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

Hi all, On Mar 28, 2009, at 9:26 AM, David Cournapeau wrote: > > I am pleased to announce the release of the rc1 for numpy > 1.3.0. You can find source tarballs and installers for both Mac OS X > and Windows on the sourceforge page: > > https://sourceforge.net/projects/numpy/ >

Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

Hi all, On Mar 28, 2009, at 9:26 AM, David Cournapeau wrote: > I am pleased to announce the release of the rc1 for numpy > 1.3.0. You can find source tarballs and installers for both Mac OS X > and Windows on the sourceforge page: > > https://sourceforge.net/projects/numpy/ >

[Numpy-discussion] DVCS at PyCon

FYI from PyCon Here at PyCon, it has been said that Python will be moving towards DVCS and will be using bzr or mecurial, but explicitly *not* git. It would seem that *git* got the "lowest" score in the Developer survey that Brett Cannon did. The reasons seem to be: * git doesn't have g

[Numpy-discussion] [Announce] Numpy 1.3.0 rc1

Hi, I am pleased to announce the release of the rc1 for numpy 1.3.0. You can find source tarballs and installers for both Mac OS X and Windows on the sourceforge page: https://sourceforge.net/projects/numpy/ The release note for the 1.3.0 release are bel

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64bit numpy?

Dinesh B Vadhia wrote: > Uhmmm! I installed 64-bit Python (2.5x) on a Windows 64-bit Vista > machine (yes, strange but true) hoping that the 32-bit Numpy & Scipy > libraries would work but they didn't. That's a totally different situation: in your case, python and numpy share the same address spa

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64bit numpy?

Uhmmm! I installed 64-bit Python (2.5x) on a Windows 64-bit Vista machine (yes, strange but true) hoping that the 32-bit Numpy & Scipy libraries would work but they didn't. From: Charles R Harris Sent: Saturday, March 28, 2009 4:28 AM To: Discussion of Numerical Python Subject: Re: [Numpy

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

Charles R Harris wrote: > > > On Sat, Mar 28, 2009 at 5:32 AM, John Reid > wrote: > > > > Charles R Harris wrote: > > What really matters is if python is 64 bits. Most 64 bit systems also > > run 32 bit binaries. > > Are you saying that

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

On Sat, Mar 28, 2009 at 5:32 AM, John Reid wrote: > > > Charles R Harris wrote: > > What really matters is if python is 64 bits. Most 64 bit systems also > > run 32 bit binaries. > > Are you saying that even if "uname -m" gives i686, I still might be able > to build a 64 bit python and numpy? > P

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

On Sat, Mar 28, 2009 at 8:32 PM, John Reid wrote: > > > Charles R Harris wrote: >> What really matters is if python is 64 bits. Most 64 bit systems also >> run 32 bit binaries. > > Are you saying that even if "uname -m" gives i686, I still might be able > to build a 64 bit python and numpy? I thi

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

Charles R Harris wrote: > What really matters is if python is 64 bits. Most 64 bit systems also > run 32 bit binaries. Are you saying that even if "uname -m" gives i686, I still might be able to build a 64 bit python and numpy? ___ Numpy-discussion

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

On Sat, Mar 28, 2009 at 8:23 PM, John Reid wrote: > David Cournapeau wrote: >> from platform import machine >> print machine() >> >> Should give you something like x86_64 for 64 bits intel/amd architecture, > > > In [3]: from platform import machine > > In [4]: print machine() > i686 > > > Now I'm

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

Charles R Harris wrote: > What platform are you on? I'm guessing Mac. You can check python on unix > type systems with > > $[char...@f9 ~]$ file `which python` > /usr/bin/python: ELF 32-bit LSB executable, Intel 80386, version 1 > (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

Charles R Harris wrote: > What platform are you on? I'm guessing Mac. You can check python on unix > type systems with > > $[char...@f9 ~]$ file `which python` > /usr/bin/python: ELF 32-bit LSB executable, Intel 80386, version 1 > (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

On Sat, Mar 28, 2009 at 5:23 AM, John Reid wrote: > David Cournapeau wrote: > > from platform import machine > > print machine() > > > > Should give you something like x86_64 for 64 bits intel/amd architecture, > > > In [3]: from platform import machine > > In [4]: print machine() > i686 > > > Now

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

David Cournapeau wrote: > from platform import machine > print machine() > > Should give you something like x86_64 for 64 bits intel/amd architecture, In [3]: from platform import machine In [4]: print machine() i686 Now I'm wondering why the OS isn't 64 bit but that's not for discussion her

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

Sorry for noise, it is my mistake. My assumption that the box is 64 bit was wrong :( At least the processors are 64 bit : Intel® Core™2 Duo Processor T9600 but uname -m reports: i686 which as far as I understand means it thinks it is a 32 bit processor. If anyone knows better please let me

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

On Sat, Mar 28, 2009 at 5:01 AM, John Reid wrote: > I imagine I'm using 64 bit numpy as I made a vanilla install from recent > source on a 64 bit box but how can I tell for sure? I have some problems > creating large arrays. > What platform are you on? I'm guessing Mac. You can check python on un

Re: [Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

On Sat, Mar 28, 2009 at 8:01 PM, John Reid wrote: > I imagine I'm using 64 bit numpy as I made a vanilla install from recent > source on a 64 bit box but how can I tell for sure? I have some problems > creating large arrays. from platform import machine print machine() Should give you something

[Numpy-discussion] How to tell whether I am using 32 bit or 64 bit numpy?

I imagine I'm using 64 bit numpy as I made a vanilla install from recent source on a 64 bit box but how can I tell for sure? I have some problems creating large arrays. In [29]: a=numpy.empty((1024, 1024, 1024), dtype=int8) works just fine In [30]: a=numpy.empty((1024, 1024, 2048), dtype=int8

Re: [Numpy-discussion] array of matrices

2009/3/27 Charles R Harris : > > On Fri, Mar 27, 2009 at 4:43 PM, Robert Kern wrote: >> >> On Fri, Mar 27, 2009 at 17:38, Bryan Cole wrote: >> > I have a number of arrays of shape (N,4,4). I need to perform a >> > vectorised matrix-multiplication between pairs of them I.e. >> > matrix-multiplicat