APPHOT/DAOPHOT Problems

Jason Quinn wrote on Apr 29, 2007

I'm running 2.12.2a on a machine and I just tried using APPHOT/DAOPHOT on it and I'm get problems I've never seen before.

The first one is that the automatic "coo" and "mag" suffixes from daofind and phot, respectively, get added to the whole filename rather than just the root filename. (e.g. "image.fits.coo.1" rather than "image.coo.1").

Secondly, the tasks are refusing to import the values of the image keywords for exposure time, obstime, etc... The name of the keyword is used instead. The keywords are definitely there in the image however.

I first noticed these problems on new data but I also tested it on old data where the tasks worked fine in the past.

Totally puzzled,
Jason

---

Valeev Azamat wrote on Apr 29, 2007

The first one is that the automatic "coo" and "mag" suffixes from daofind and phot, respectively, get added to the whole filename rather than just >the root filename. (e.g. "image.fits.coo.1" rather than "image.coo.1").

I did not work in other IRAF version and
do not see this problem. For solving
the first problem use:
files *%.fits% > filelist
It create list of fits files without extension

Secondly, the tasks are refusing to import the values of the image keywords for exposure time, obstime, etc... The name of the keyword is used instead. The keywords are definitely there in the image however.

If you see in datapars config file
you may see where:
itime,r,h,1.0,,,'Exposure time'
exposure,s,h,'',,,'Exposure time image header keyword'

In datapars help file you may read:
If exposure is undefined or not present in the image header a warning message is issued and the value of itime is used. The itime units are arbitrary but must be consistent for images analyzed together.
You may use any of this parameters. (exposure<->itime,filter <->ifilter,obstime <-> otime,airmass <-> xairmass)
I think it is easier use keyword name, which are
standart for every telescope.

Azamat :wink:

---

Jason Quinn wrote on Apr 29, 2007

I'm writing an update to my post... (ignore me for now)

---

Jason Quinn wrote on Apr 29, 2007

Okay. Partly a false alarm. Things work how they used to. The phot tasks don't strip the image extension off by default. I was falsely remembering that they did. Plus I was mis-remembering how to use pdump. I was thinking I could pdump obstime when I want to pdump otime. I guess that's what being away from IRAF for 9 months will do to a person.

While it is up, these tasks SHOULD strip the image extension when default is used. Here's the help page for daofind:

output = "default"
The name of the results file or the results directory. If
output is "default", "dir$default" or a directory specification
then a results file name of the form dir$root.extension.version
is constructed, where dir is the directory, root is the root
image name, extension is "coo" and version is the next
available version number for the file. If the output string is
undefined then no output file is created. One output file is
created for every input image.

The other tasks agree with this too.

Jason

---

Last post on Apr 29, 2007