Welcome to iraf.net Thursday, March 28 2024 @ 08:56 PM GMT
Hooloovoo |
02/06/2007 12:51PM (Read 3639 times)
|
|
|
Status: offline
Registered: 05/30/2006
Posts: 7
|
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:[i:066927664a]im> hedit ("*.fits", "TELESCOP","(TELESCOP == 'Telescope Name' ? 'XX' : TELESCOP)", add=yes, addonly=no,delete=no, verify=no, show=no, update=yes)[/i:066927664a]
[b:066927664a]Unable to open parameter file `uparm$imlhedit.par'.[/b:066927664a]Does anyone know what this is about?thanks.
|
|
|
|
fitz |
02/06/2007 12:51PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
If you moved [b:9d9ea5386e]everything[/b:9d9ea5386e] 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
|
|
|
|
Hooloovoo |
02/06/2007 12:51PM
|
|
|
Status: offline
Registered: 05/30/2006
Posts: 7
|
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
|
|
|
|
fitz |
02/06/2007 12:51PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
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
|
|
|
|
| |
|
Content generated in: 0.12 seconds |
|