---------- Forwarded message ----------
From: Mike Ressler <[EMAIL PROTECTED]>
Date: Jul 25, 2006 12:17 PM
Subject: Re: ***[Possible UCE]*** [Numpy-discussion] Bug in memmap/python allocation code?
To: Travis Oliphant < [EMAIL PROTECTED]>
Cc: Numpy-discussion@lists.sourceforge.net
On 7/24/06,
Travis Oliphant <[EMAIL PROTECTED]
> wrote:
Mike Ressler wrote:
> I'm trying to work with memmaps on very large files, i.e. > 2 GB, up
> to 10 GB.
Can't believe I'm really the first, but so be it.
I just discovered the problem. All the places where
PyObject_As<Read/Write>Buffer is used needs to have the final argument
changed to Py_ssize_t (which in arrayobject.h is defined as int if you
are using less than Python 2.5).
This should be fixed in SVN shortly....
Yeess! My little script can handle everything I've thrown at it now. It can read a 10 GB raw file, strip the top 16 bits, rearrange pixels, byte swap, and write it all back to a 5 GB file in 16 minutes flat. Not bad at all. And I've verified that the output is correct ...
If someone can explain the rules of engagement for Lightning Talks, I'm thinking about presenting this at SciPy 2006. Then you'll see there is a reason for my madness.
Thanks for your help and the quick solution. FWIW, I got my copy of the book a couple of weeks ago; very nice.
Mike
--
[EMAIL PROTECTED]
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion