🚀 go-pugleaf

I tried reading the test defective FITS files  generated by Barry
Schlesinger (see previous post to this newsgroup) to see if the FITSIO
subroutine package detected the errors.   I tried reading each pseudo
FITS file with a simple program that just lists the header of a FITS
file.  The following list shows the error message that was returned by
FITSIO for each file.   FITSIO did very well and found all the errors,
except one:  it didn't complain if the first keyword was 'SIMPLE =
W';  it just assumed that if SIMPLE was not true, then it must be false.
I'll add this check to the next version of FITSIO.

-Bill Pence
--------------------------------------------------------------------------

List of error responses generated by FITSIO when trying to read test defective
FITS files generated by Barry Schlesinger

FILENAME       FITSIO RESPONSE
--------       ---------------
good.tst
        No errors detected; OK since this is a legal FITS file

different.tst:
	Error Status Returned :  210
	Missing "= " in cols 9-10

nosimple.tst
	Error Status Returned :  221
	SIMPLE keyword not found

simplew.tst
        No errors detected;  didn't detect SIMPLE = W;  FITSIO should
        have complained about this.

simplef.tst
        No errors detected;  didn't complain about SIMPLE = F; OK

bitpixq2
	Error Status Returned :  211
	Illegal BITPIX keyword value

bitpix13
	Error Status Returned :  211
	Illegal BITPIX keyword value

noequal.tst
	Error Status Returned :  210
	Missing "= " in cols 9-10

qin10.tst
	Error Status Returned :  210
	Missing "= " in cols 9-10

extraxis.tst
	No errors detected;  OK since this is a legal FITS file

missaxis.tst
	Error Status Returned :  224
	NAXISnnn keywords not found

simple2nd.tst
	Error Status Returned :  210
	Missing "= " in cols 9-10

shuffle.tst
	Error Status Returned :  222
	BITPIX keyword not found

latenaxis.tst
	Error Status Returned :  223
	NAXIS  keyword not found

endequal.tst
	No errors detected;  OK since this is a legal FITS file (?).