Hi,
There are a few big EIS fits files which are not easy to be processed by "eis_prep", for example:
20/eis_l0_20070820_170353.fits.gz 122M
21/eis_l0_20070821_000022.fits.gz 118M
21/eis_l0_20070821_133226.fits.gz 117M
- Click to show more fits files
- 22/eis_l0_20070822_023009.fits.gz 116M
- 23/eis_l0_20070823_191420.fits.gz 94M
- 24/eis_l0_20070824_001531.fits.gz 92M
- 24/eis_l0_20070824_105128.fits.gz 120M
- 25/eis_l0_20070825_015152.fits.gz 99M
- 25/eis_l0_20070825_050529.fits.gz 95M
- 25/eis_l0_20070825_093750.fits.gz 89M
- 26/eis_l0_20070826_005803.fits.gz 97M
- 26/eis_l0_20070826_055213.fits.gz 92M
- 27/eis_l0_20070827_045520.fits.gz 97M
- 27/eis_l0_20070827_170835.fits.gz 81M
- 27/eis_l0_20070827_210723.fits.gz 79M
- 28/eis_l0_20070828_005937.fits.gz 72M
- 22/eis_l0_20070822_023009.fits.gz 116M
These fits files are mostly generated by study eg. "HPW001_FULLCCD_v2": doing "full-ccd" scan (with often over 80 raster positions).
The typical error message is: "unable to allocate memory to make array". However, the machine that running "eis_prep" has fairly big enough memory (4GB). One way to let "eis_prep" keep running is probably to do only DC-removal and Abs calibration, not to do CR and HP removal, :-(
Questions:
- Is there any way to do 'eis_prep' with these big fits files? Or,
- Do we need to suggest that normally try to avoid using full-ccd scan with too many raster postions?
Regards,
JianSun 08-May-2024 05:47
Hi, Jian
This is starting to become a big problem, and I think you're asking the right questions.
However, I don't think we should stop taking large data because the current software doesn't allow us to analyse it. This just means we need to think about . We want to take the best data we can and worry about analysing it later. You never know when an instrument/satellite can fail.
This sounds like a major issue for the team meetings in October.
In the meantime, if anyone has comments, please start making them! This is something that really needs to be sorted out.
--David R Williams
, 19-Sep-2007