`hedit` problem in new IRAF installation
Hooloovoo wrote on Feb 06, 2007
Hi,
I am running a difference image reduction pipeline that uses IRAF/DaoPhot for the initial photometry on the images as well as header editing etc. Everything works fine on the old machine that I was running it on but I recently transferred the codes on a new server, reinstalled the relevant packages including IRAF and the pipeline crashes (which is not unexpected). The new machine runs Fedora Core 4. The error that I get is when I call the hedit command from within IRAF:
im> hedit ("*.fits", "TELESCOP","(TELESCOP == 'Telescope Name' ? 'XX' : TELESCOP)", add=yes, addonly=no,delete=no, verify=no, show=no, update=yes)
Unable to open parameter file `uparm$imlhedit.par'.
Does anyone know what this is about?
thanks.
I am running a difference image reduction pipeline that uses IRAF/DaoPhot for the initial photometry on the images as well as header editing etc. Everything works fine on the old machine that I was running it on but I recently transferred the codes on a new server, reinstalled the relevant packages including IRAF and the pipeline crashes (which is not unexpected). The new machine runs Fedora Core 4. The error that I get is when I call the hedit command from within IRAF:
im> hedit ("*.fits", "TELESCOP","(TELESCOP == 'Telescope Name' ? 'XX' : TELESCOP)", add=yes, addonly=no,delete=no, verify=no, show=no, update=yes)
Unable to open parameter file `uparm$imlhedit.par'.
Does anyone know what this is about?
thanks.
Mike Fitzpatrick wrote on Feb 06, 2007
If you moved everything to the new machine then it probably means you're still using your old login.cl file. This file contains a path to the 'uparm' directory and when you move machines the path may become invalid. Simply do a new MKIRAF to recreate the login.cl for the new machine.
Note also that if you're using .imh images instead of FITS files there can be a similar problem in locating the .pix pixel files. Post back if you have this problem, the short answer is to edit the 'i_pixfile' header heyword with the new path in each of the images.
Cheers,
-Mike
Note also that if you're using .imh images instead of FITS files there can be a similar problem in locating the .pix pixel files. Post back if you have this problem, the short answer is to edit the 'i_pixfile' header heyword with the new path in each of the images.
Cheers,
-Mike
Hooloovoo wrote on Feb 06, 2007
Thanks fitz! That seems to have squashed that bug in the program.
Now it gets stuck at:
da> Fitting the PSF model to the groups of stars
da> associated with the PSF stars on the reference frame...
da>
da> >>> more than one `mode' param
Now it gets stuck at:
da> Fitting the PSF model to the groups of stars
da> associated with the PSF stars on the reference frame...
da>
da> >>> more than one `mode' param
Mike Fitzpatrick wrote on Feb 06, 2007
The '>>>' is the CL command-continuation prompt, my guess is you've done
something like forgotten a closing parenthesis on a task call or have an unescaped newline and the script is getting confused. You can set the 'd_trace' toggle to trace the execution of a script and see where this message is coming from. Complaints about params can rarely be a corrupted uparm file, try unlearning the task to clear it.
Cheers,
-Mike
something like forgotten a closing parenthesis on a task call or have an unescaped newline and the script is getting confused. You can set the 'd_trace' toggle to trace the execution of a script and see where this message is coming from. Complaints about params can rarely be a corrupted uparm file, try unlearning the task to clear it.
Cheers,
-Mike
Last post on Feb 06, 2007