Repository navigation
Issue with astropy.io.fits and large arrays - #839
Conversation
|
I'm also seeing issues with a table that is valid between memory mapping and no memory mapping: But the table is 6Gb, so not easy to share (nevertheless I can put it online if needed) |
|
I think I've seen this before. First of all the entire file isn't being written in the first place. I think this is that thing where it keeps writing and then the file pointer overflows. It was a bug in Numpy that I fixed at some point... |
|
Though I thought PyFITS had a workaround for it too, so I'll have to check on that as well. |
|
Well I'm not getting this on Linux with either Numpy 1.6.2 or 1.7.0. So once again the problem seems to be something particular with OSX 💢 |
|
I remember now, this was the issue: http://projects.scipy.org/numpy/ticket/2114 Yay OSX \o/ |
|
Yup. That's gotta be it: Now I'm just concerned because I could have sworn I put a workaround to this in pyfits. I thought there was even a regression test, but now I can't find it... |
|
I've attached a workaround for this issue. With this fix the test given in the original issue now works as expected. Some more complex tests work too. I have not added a unit test for this issue because it takes a little time depending on filesystem I/O throughput and requires some 4GB of disk space. Perhaps in the future we should consider adding a test marker for "big" tests that are normally skipped by default. |
…o removed a Sphinx-specific directive from the changelog (just for now--I need to revist whether or not we want to be able to render the changelog without Sphinx).
|
This works for me! Feel free to merge :) |
|
Thanks--wasn't sure if I'd hear back from you on this or not since I know you were on vacation. So I was leaving it open 'til the last minute. |
Issue with astropy.io.fits and large arrays
|
@taldcroft is on vacation, not me :) |
|
Damn! Getting my Toms mixed up 😫 |
Issue with astropy.io.fits and large arrays Conflicts: CHANGES.rst
I'm seeing the following issue with astropy.io.fits:
This is on MacOS 10.8 with 64Gb of RAM.
@iguananaut - I know you want issues to be opened on the pyfits tracker, but this is an issue that IMHO should be fixed in 0.2.1 (if it's an easy fix) so I need to open it here so we can keep track of it.