FITS problem with 2.15.1a and OSX 10.6.x?
npirzkal wrote on Jun 02, 2011
I am having recurring problems running long IRAF/Pyraf python scripts that access many FITS files.
At some point, some IRAF tasks fails to be able to open (existing and well formatted) FITS files even though they are indeed where they are.
Running the task out of the Pyraf script works fine.
It looks like it is a subtle issue between Pyraf/IRAF/OSX and I do not know if anyone else has noticed this?
I just found out that if I add and iraf.flprc() before calling the offending iraf/pyraf command things run fine.
At some point, some IRAF tasks fails to be able to open (existing and well formatted) FITS files even though they are indeed where they are.
Running the task out of the Pyraf script works fine.
It looks like it is a subtle issue between Pyraf/IRAF/OSX and I do not know if anyone else has noticed this?
I just found out that if I add and iraf.flprc() before calling the offending iraf/pyraf command things run fine.
Mike Fitzpatrick wrote on Jun 02, 2011
What exactly is the "offending iraf/pyraf command"?? Are the FITS files accessed by compiled IRAF tasks or python directly (e.g. via pyfits)? Is pyraf interpreting a .cl script or is it a python script itself? What do you mean by "running the task out of the pyraf script", does this mean running a CL?? When you say "fail to open", is this for input or output? What exactly is the error message (and from what task)??
Last post on Jun 02, 2011