For hints on using DS9 without IRAF, check out Adam's DS9 tips page Instructions for dealing with IRAF errorsIf you experience errors containing $uparm, make sure you have write permissions to your home and imdir directories, which are set on lines 7 and 8 of your login.cl file.To install IRAF, run mkiraf, which will create a new login.cl for you. You may have to change your imdir to "home$images/" or something similar. You must search for the line #set imtype "imh" and change it to read set imtype "fits" (remove the # at the beginning of the line). If you have trouble with .imh files showing up instead of .fits files:
IRAF quick tips
Matching Guider Images to Science ImagesInstead of going through each individual file's header, I recommend using these commands or similar:imhead proc-*.fits[0] lo+ | egrep "Pixel\ file\|UTTIME" imhead e*.fits lo+ | grep -E "Pixel\ file\|UTC-OBS" If you're curious about what those commands mean, read on.You should already be familiar with the imhead command, which with the long option enabled prints the full header. The [0] appended to the end of the filename chooses the first extension in the fits image. A fits file is capable of holding many extensions, i.e. many images, in one file. In the case of the Echelle guider camera, the proc-[something].fits files have the slit superimposed on the sky image as the first extension, and the slit mask image as the second extension.The grep command outputs all lines containing a regular expression from its input. A regular expression is a special pattern matching expression. In this case, we have "Pixel\ file\|UTC-OBS", which means we are searching for lines with the string Pixel file or UTC-OBS. The backslash before the space escapes the space so that IRAF doesn't think you are giving it another command. Similarly, we must escape the or operator | (though I'm not entirely certain why - this is not standard behavior). egrep is equivalent to grep -E for older versions of grep that do not allow the option syntax. |