CCDHEDIT: Getting the right keyword type

Frank Valdes wrote on Jun 02, 1998

Q:  It seems the task CCDHEDIT insists on writing any header keyword
as a string even though I specify type=real....

    NOAO PC-IRAF Revision 2.11.1 EXPORT Mon Jan 26 13:32:19 MST 1998


A:  If you are adding/creating a new keyword then the type specification
works fine.  However, it is a quirk of IRAF that you cannot change
an existing string type keyword to a numeric keyword.  The same
behavior also applies to HEDIT.  So you should delete the keyword
you want to set to a real value and then use CCDHEDIT.

---

Octavi Fors Aldrich wrote on Jun 04, 1998

Hi.

I've been using FITPSF task for a long time. Up to now its 0.001-pixel
precision in the determination of (XCENTER,YCENTER) was enough for me. But
now I would be very interested in more accurate results.

Is there any way to increase the (XCENTER,YCENTER) precision?
Any "hidden" parameter is needed to be changed for further compilation?
Is it really necessary to recompile some code?

I would be very thankful if you could give me some hints about it.


 Thanks in advance,


=================================================================

Octavi Fors

Astronomy Department
Physics Faculty
Diagonal Av., 647
08028 Barcelona
SPAIN

=================================================================

---

Last post on Jun 04, 1998