cmf files break FITS standard

[Paul Price]

John Lucey writes:

"Another problem I had was when I try to overlay the objects in
test.CHIP3.cmf on the input image with GAIA. This fails because
according to our local fits expert (Peter Draper) the .cmf breaks the
fits standard. Apparently the primary HDU header should not have various
header cards like NAXIS1=xxxx, etc when NAXIS=0. Apparently there is
image information when there is no image??? I've no idea whether
this is right or not but Peter is usually right!"

I ran a cmf file through the FITS verifier (​http://fits.gsfc.nasa.gov/fits_verify.html), and it produced 4 errors and 1 warning:

* Warning: Keyword #97, EXTNAME should not be used in a primary array.
* Error: Keyword #12, NAXIS1 is duplicated or out of order.
* Error: Keyword #12, NAXIS1 is not allowed (with n > NAXIS =0).
* Error: Keyword #13, NAXIS2 is duplicated or out of order.
* Error: Keyword #13, NAXIS2 is not allowed (with n > NAXIS =0).

[...]

HDU# Name (version) Type Warnings Errors
1 Primary Array 1 4
2 SkyChip.psf Binary Table 0 0

Breaking the FITS standard prevents other tools from working on our data.

[eugene]

We've changed NAXIS1,NAXIS2 to IMNAXIS1,2.

I'm going to leave this bug unresolved until we deal with the EXTNAME complaint: we need to be sure addstar is not going to expect that field for the PHU header.

[eugene]

EXTNAME is no longer be pushed into the PHU headers