🚀 go-pugleaf

In article <pence.711826605@heawk1>, pence@heawk1.gsfc.nasa.gov ( William Pence) writes...
> 
>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
> 

This is something of an understatement, as the file isn't close to 
FITS.

> ... [results for other files] ...
.
>shuffle.tst
>	Error Status Returned :  222
>	BITPIX keyword not found

Actually there is a BITPIX keyword in the file, just in the wrong 
place.  But a reader shouldn't be expected to find it.

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

As above.

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

Not exactly.  The = in column 9 of the END card image shouldn't be
there.  Readers probably should provide a warning.  Validation
software certainly should.  As is noted in the README.FIRST, Don Wells
reports that some readers have crashed on this syntax. 

				Barry Schlesinger
				FITS Support Office