Re: [Numpy-discussion] Bug in memmap/python allocation code?

2006-07-27 Thread Robert Kern
Mike Ressler wrote: My apologies if this is a duplicate - my first attempt doesn't seem to have gone back to the list. SF if being nasty with GMail. I'll have to speed up moving the list to scipy.org. If someone can explain the rules of engagement for Lightning Talks, I'm thinking about

[Numpy-discussion] Bug in memmap/python allocation code?

2006-07-26 Thread Mike Ressler
My apologies if this is a duplicate - my first attempt doesn't seem to have gone back to the list.-- Forwarded message --From: Mike Ressler [EMAIL PROTECTED]Date: Jul 25, 2006 12:17 PMSubject: Re: ***[Possible UCE]*** [Numpy-discussion] Bug in memmap/python allocation code

Re: [Numpy-discussion] Bug in memmap/python allocation code?

2006-07-25 Thread Karol Langner
On Tuesday 25 July 2006 02:36, Mike Ressler wrote: I'm trying to work with memmaps on very large files, i.e. 2 GB, up to 10 GB. The files are data cubes of images (my largest is 1290(x)x1024(y)x2011(z)) and my immediate task is to strip the data from 32-bits down to 16, and to rearrange some

[Numpy-discussion] Bug in memmap/python allocation code?

2006-07-24 Thread Mike Ressler
I'm trying to work with memmaps on very large files, i.e. 2 GB, up to 10 GB. The files are data cubes of images (my largest is 1290(x)x1024(y)x2011(z)) and my immediate task is to strip the data from 32-bits down to 16, and to rearrange some of the data on a per-xy-plane basis. I'm running this