Cannot close file error?
Elden Paul Iverson wrote on Nov 05, 2007
I received the following error.
ERROR: Cannot close file (flatR-66612cb.fits)
"rfits (s1,"","flatR-"//n)"
called as: 'ap_rfits_v_1 ()'
I have run this script many times without any problems. I don't even know where this flatR-66612cb.fits is coming from. Earlier the same error was occuring but in a different place. What is happening?
Thanks.
Paul Iverson
ERROR: Cannot close file (flatR-66612cb.fits)
"rfits (s1,"","flatR-"//n)"
called as: 'ap_rfits_v_1 ()'
I have run this script many times without any problems. I don't even know where this flatR-66612cb.fits is coming from. Earlier the same error was occuring but in a different place. What is happening?
Thanks.
Paul Iverson
Mike Fitzpatrick wrote on Nov 05, 2007
There are no known issues with RFITS like this and since you mention a script I suspect it's either a scripting error causing a file descriptor leak (e.g. you use list pointers to loop over filelists but don't 'close' them when done with the loop (by e.g. list="") and so they build up), or perhaps a disk is filling up, or lastly a problem in the FITS file itself.
Are you able to do things like IMSTAT and IMHEAD directly on the file?
-Mike
Are you able to do things like IMSTAT and IMHEAD directly on the file?
-Mike
Elden Paul Iverson wrote on Nov 05, 2007
Mike-
We have found that we are filling our tmp/ folder with .fits images. I was under the impression that these should have been deleted automatically. I think this has something to do with our scripts but we don't know how to fix them so that the clean the tmp/ directory. Do you have any suggestions. This has lead to the corruption (possibly) of one hard drive and the near filling of 2 others before we caught it.
Thanks,
-Paul
We have found that we are filling our tmp/ folder with .fits images. I was under the impression that these should have been deleted automatically. I think this has something to do with our scripts but we don't know how to fix them so that the clean the tmp/ directory. Do you have any suggestions. This has lead to the corruption (possibly) of one hard drive and the near filling of 2 others before we caught it.
Thanks,
-Paul
Last post on Nov 05, 2007