Note that this section describes KAPPA FITSDIN rather than CONVERT FITS2NDF because at the time of writing the latter aborts when presented with an ING nearly-FITS file. The underlying problem is with the ING file rather than FITS2NDF. It may be possible to switch to using FITS2NDF when it has been enhanced to handle ING nearly-FITS files. ACD, 11/5/99.
The CCD images that you plan to reduce may be available as FITS files (see Section 6.2) which are already resident on magnetic disk, as is the case for the examples provided with this cookbook. Most Starlink software can read data files in a variety of formats, including FITS. However, it is most simple, convenient and efficient to convert the files to Starlink’s NDF (-dimensional Data Format; see SUN/33) format at the outset.
If you have not already done so, you should copy the example data to a convenient directory where you can work on them, as described in Section 8.1. Make this directory your current directory, then proceed as follows.
The header records will be listed to the terminal. This output should look similar to Figure 9.
fmtcnv=yes specifies that INTEGER data arrays in the input files will be converted to
REAL arrays in the output NDF files. The keywords in the FITS file will be listed
to the terminal and NDF file
ngc2336_r_1.sdf should be created in your current
hdstraceutility. Simply type:
(note that the ‘
.sdf’ file-extension can be omitted).
hdstrace is fully documented in
Note the use of the asterisk (‘
*’) as a wild card: all the files in the directory with names ending in
.fit’ are converted without having to explicitly specify their file names. The file specification
*.fit’ is enclosed in quotes to ensure that the asterisk is passed to
fitsdin rather than
being trapped and interpreted by the Unix shell. The use of Starlink applications from
Unix shell scripts is discussed further in SC/4: C-shell Cookbook. The
specifies that the output file name is to be constructed automatically from the input file