Re: [Numpy-discussion] Segmentation Fault with Numeric 24.2 on Mac OS X 10.4 Tiger (8.7.0)

Hi Chris, I tried your suggestion of installing and running the pre-built packages at . I am sorry to report that the pre-built MacPython and Numeric 24.2 package did not work. I get the same "Segmentation Fault" that I got when I built Python 2.4.3 and

Re: [Numpy-discussion] numpy.ascontiguousarray on byteswapped data !?

Travis Oliphant wrote: > Sebastian Haase wrote: >> Hi, >> Does numpy.ascontiguousarray(arr) "fix" the byteorder when arr is >> non-native byteorder ? >> >> If not, what functions does ? >> > > It can if you pass in a data-type with the right byteorder (or use a > native built-in data-type). >

Re: [Numpy-discussion] format typestr for "String" ( 10 strings: '10a80' ) gives just 'None'

Travis Oliphant wrote: > Sebastian Haase wrote: >> This is what I get: It claims that the 'title' field (the last one) >> is 10 times 'S80' but trying to read that array from the first (and >> only) record (a.Mrc._hdrArray.title[0]) I just get None... >> > Hopefully that problem is resolved

Re: [Numpy-discussion] numpy.ascontiguousarray on byteswapped data !?

Sebastian Haase wrote: > Hi, > Does numpy.ascontiguousarray(arr) "fix" the byteorder when arr is non-native > byteorder ? > > If not, what functions does ? > It can if you pass in a data-type with the right byteorder (or use a native built-in data-type). In NumPy, it's the data-type that car

[Numpy-discussion] numpy.ascontiguousarray on byteswapped data !?

Hi, Does numpy.ascontiguousarray(arr) "fix" the byteorder when arr is non-native byteorder ? If not, what functions does ? - Sebastian Haase - Using Tomcat but need to do more? Need to support web services, security? Get s

Re: [Numpy-discussion] format typestr for "String" ( 10 strings: '10a80' ) gives just 'None'

On Thursday 10 August 2006 16:57, Travis Oliphant wrote: > Sebastian Haase wrote: > > Hi, > > trying to convert my memmap - records - numarray code for reading a > > image file format (Mrc). > > There are 10 fields of strings (each 80 chars long) in the header: > > in numarray I used the format st

[Numpy-discussion] format typestr for "String" ( 10 strings: '10a80' ) gives just 'None'

Hi, trying to convert my memmap - records - numarray code for reading a image file format (Mrc). There are 10 fields of strings (each 80 chars long) in the header: in numarray I used the format string '10a80' This results in a single value in numpy. Same after changing it to '10S80'. Am I doing

Re: [Numpy-discussion] Problem with numpy.linalg.inv in numpy 1.01b on Mac OS X 10.4 Tiger (8.7.0)

Sasha wrote: > I see that Travis just fixed that by making context optional > . I am not sure > it is a good idea to allow use of ufuncs for which domain is not > defined in ma. This may lead to hard to find bugs coming from ma > arrays with n

Re: [Numpy-discussion] Problem with numpy.linalg.inv in numpy 1.01b on Mac OS X 10.4 Tiger (8.7.0)

I see that Travis just fixed that by making context optional . I am not sure it is a good idea to allow use of ufuncs for which domain is not defined in ma. This may lead to hard to find bugs coming from ma arrays with nans in the data. I wou

Re: [Numpy-discussion] Problem with numpy.linalg.inv in numpy 1.01b on Mac OS X 10.4 Tiger (8.7.0)

Hi Sasha, > Inverting a matrix with masked values does not make much sense. Call > "filled" method with an appropriate fill value before passing the > matrix to "inv". In principle you are right, but even though I use masked arrays in this operation, when the operation itself is done no masked va

[Numpy-discussion] Numarray compatibility module available

I've just finished a first version of the numarray compatibility module. It does not include all the names from the numarray name-space but it does include the most important ones, I believe. It also includes a slightly modified form of the numarray type-objects so that NumPy can recognize t

Re: [Numpy-discussion] Problem with numpy.linalg.inv in numpy 1.01b on Mac OS X 10.4 Tiger (8.7.0)

Inverting a matrix with masked values does not make much sense. Call "filled" method with an appropriate fill value before passing the matrix to "inv". On 8/10/06, Daran L. Rife <[EMAIL PROTECTED]> wrote: > Hello, > > I am a veteran user of Numeric and am trying > out the latest version of numpy (

Re: [Numpy-discussion] Problem with numpy.linalg.inv in numpy 1.01b on Mac OS X 10.4 Tiger (8.7.0)

On Thu, 10 Aug 2006 07:33:44 -0600 (MDT) "Daran L. Rife" <[EMAIL PROTECTED]> wrote: > Hello, > > I am a veteran user of Numeric and am trying > out the latest version of numpy (numpy 1.01b) > on Mac OS X 10.4 Tiger (8.7.0). > > When trying to invert a matrix with > numpy.linalg.inv I get the fol

[Numpy-discussion] SciPy 2006 LiveCD torrent is available

For those not able to make SciPy 2006 next week, or who would like to download the ISO a few days early, its available at http://code.enthought.com/downloads/scipy2006-i386.iso.torrent. We squashed a lot onto the CD, so I also had to trim > 100 MB of packages that ship with the standard Ubuntu

Re: [Numpy-discussion] Segmentation Fault with Numeric 24.2 on Mac OS X 10.4 Tiger (8.7.0)

Hi Daran, I fortunately never had the need to run different versions in parallel, so I basically removed the earlier versions of numpy. However, as you possibly know, you can build wrapper functions for fortran code with f2py (which is now shipped with numpy). And that is where I got the segfault

Re: [Numpy-discussion] Segmentation Fault with Numeric 24.2 on Mac OS X 10.4 Tiger (8.7.0)

Hi Chris, Thanks very much for your reply. My apology for the confusion. To be clear, I am a veteran user of Numeric not numpy. I tried installing four versions of Numeric: 23.8, 24.0, 24.1, and 24.2. My Python distro is built from source, using the GCC 4.0.1 suite of compilers. I am running all o

Re: [Numpy-discussion] Segmentation Fault with Numeric 24.2 on Mac OS X 10.4 Tiger (8.7.0)

Daran L. Rife wrote: > Many thanks for the reply. This was my first attempt > to build and use numpy; "numpy" used to be a generic name for the Numerical extensions to Python. Now there are three versions: "Numeric": The original, now at version 24.2 This is probably the last version that will

Re: [Numpy-discussion] Segmentation Fault with Numeric 24.2 on Mac OS X 10.4 Tiger (8.7.0)

Hi Hanno, > I had a similar behaviour when I tried to use module compield with an > older f2py with a newer version of numpy. So is it maybe possible that > some *.so files are used from an earlier build? Many thanks for the reply. This was my first attempt to build and use numpy; I have no prev

Re: [Numpy-discussion] Segmentation Fault with Numeric 24.2 on Mac OS X 10.4 Tiger (8.7.0)

Daran, I had a similar behaviour when I tried to use module compield with an older f2py with a newer version of numpy. So is it maybe possible that some *.so files are used from an earlier build? Hanno "Daran L. Rife" <[EMAIL PROTECTED]> said: > Hi group, > > Sorry, but there was an error on

Re: [Numpy-discussion] Segmentation Fault with Numeric 24.2 on Mac OS X 10.4 Tiger (8.7.0)

Hi group, Sorry, but there was an error on my previous message, 2nd paragraph, 2nd setence. It should read: Unfortunately, I am experiencing a problem that I cannot sort out. I am running Python 2.4.3 on a Mac G5 running OS X 10.4 Tiger (8.7.0), using gcc version 4.0.1, and the Apple vecLib.frame

[Numpy-discussion] Problem with numpy.linalg.inv in numpy 1.01b on Mac OS X 10.4 Tiger (8.7.0)

Hello, I am a veteran user of Numeric and am trying out the latest version of numpy (numpy 1.01b) on Mac OS X 10.4 Tiger (8.7.0). When trying to invert a matrix with numpy.linalg.inv I get the following error: > Traceback (most recent call last): File "./bias_correction.py", line 381, in

Re: [Numpy-discussion] Change of signature for copyswap function ?

Pierre Barbier de Reuille wrote: > Hi, > > in my documentation, the copyswap function in the PyArray_ArrFuncs > structure is supposed to have this signature: > > copyswap (void) (void* dest, void* src, int swap, int itemsize) > > However, in the latest version of NumPy, the signature is: > > copysw

[Numpy-discussion] Change of signature for copyswap function ?

Hi, in my documentation, the copyswap function in the PyArray_ArrFuncs structure is supposed to have this signature: copyswap (void) (void* dest, void* src, int swap, int itemsize) However, in the latest version of NumPy, the signature is: copyswap (void) (void*, void*, int, void*) My question