For Starlink the FITS extension is secondary to the WCS definition. If
you run "ndftrace fullframe" on the file you will see the world
coordinates information listed and one of those attributes will be
epoch. This is what ndf2fits uses to fill in the DATE-OBS header to
ensure that the WCS in the FITS file is consistent.
If you converted from FITS then the epoch header should have been
filled in from the DATE-OBS header originally. The DATE-OBS in the
FITS header is just a memory of the original FITS header rather than
an expression of the WCS. I assume the header in this case did not
come from a FITS file.
Use wcsattrib (kappa command) to set the epoch from the DATE-OBS
header (use FITSVAL to get the value in a shell variable).
On Sun, Jun 17, 2012 at 9:53 AM, Eduardo Unda-Sanzana
<[log in to unmask]> wrote:
> I have an NDF file with this date in the header:
> DATE-OBS= '2012-06-02T04:14:08' /YYYY-MM-DDThh:mm:ss observation start, UT
> I'm converting it to a FITS file with NDF2FITS. After conversion this date is in the header:
> DATE-OBS= '2000-01-01T12:09:37.679' / Date of observation
> Also, an entry is added for the time when the conversion was made:
> DATE = '2012-06-17T16:46:20' / file creation date (YYYY-MM-DDThh:mm:ss UT)
> Any idea of what's going on?
> Starlink User Support list
> For list configuration, including subscribing to and unsubscribing from the list, see
Starlink User Support list
For list configuration, including subscribing to and unsubscribing from the list, see