Re: FITS IO Problem [message #70656 is a reply to message #70655] |
Sat, 24 April 2010 13:08   |
Craig Markwardt
Messages: 1869 Registered: November 1996
|
Senior Member |
|
|
On Apr 24, 9:18 am, John B <bochan...@gmail.com> wrote:
> On Apr 24, 8:09 am, wlandsman <wlands...@gmail.com> wrote:
>
>>> Readfits.pro is choking since this isn't a standard fits file (NAXIS
>>> isn't defined). Is there another one I can use?
>
>> There is a nice (non-IDL) program FITSVerify ( http://heasarc.gsfc.nasa.gov/docs/software/ftools/fitsverify /) to
>> check the validity of a FITS file. You can also upload your FITS
>> file to the online verifier.
>
> Cool. I submitted it and got this error:
>
> File name: test.fits
> Run Number 8232
>
> fitsverify 4.15 (CFITSIO V3.181)
> --------------------------------
>
> 2 Header-Data Units in this file.
>
> =================== HDU 1: Primary Array ===================
>
> 1 | SIMPLE = T /Dummy Created by MWRFITS v1.4a
> 2 | BITPIX = 8 /Dummy primary header created by
> MWRFITS
> 3 | NAXIS = 0 /No data is associated with this
> header
> 4 | EXTEND = T /Extensions may (will!) be
> present
> 5 | END
>
> 5 header keywords
>
> Null data array; NAXIS = 0
>
> =================== HDU 2: BINARY Table ====================
>
> *** Error: checking data fill: tried to move past end of file
> *** Error: String in row #3, column #3 contains non-ASCII text.
> (Other rows may have errors).
>
> I don't know entirely how to interpret this.
>
>
>
>> Does MWRFITS work with the simple examples provided in the
>> documentation?
>
> Yes, MWRFITS is working for other applications on my system.
>
>
>
>> You wouldn't be using GDL (the free IDL clone) rather than IDL, would
>> you? I recently discovered that GDL has a slightly different
>> treatment of nested loops than IDL, that led to disastrous
>> consequences for a different set of FITS I/O routines.
>
> Nope... I am using IDL.
>
> --Wayne
Are you by any chance overwriting an existing file? To me it looks
like you attempted to write a file, but it got stopped after writing
the primary extension. If the bits from the previous existing file
are still there, then it would look like a bogus 2nd FITS extension.
Craig
|
|
|