PÎ not reading FIT files generated by CCDCAP (QHY cams)

[Foton]

Hi all,
I have problems trying to open FIT files generated by CCDCAP the standard capture sw for QHY cameras:

C:/Documents and Settings/.../My Documents/My Pictures/Astrofoto/M51/M51_00000.FIT
Reading FITS: 16-bit integers, 1 channel(s), 1392x1024 pixels:   1%
*** PCL Exception: PCL FITS Format Support: FITS file read error:
C:/Documents and Settings/.../My Documents/My Pictures/Astrofoto/M51/M51_00000.FIT
CFITSIO error message stack:
01 : Error reading data buffer from file:
02 : C:\Documents and Settings\...\My Documents\My Pictures\Astrofoto\M51
03 : \M51_00000.FIT
04 : Error reading elements 1 thru 1392 from image (ffgcld).
<* failed *>

Any idea ?
Many thanks. JLuis.

[Niall Saunders]

Hi,

Have you tried 'verifying' your FITS files?

Have a look at
<http://fits.gsfc.nasa.gov/fits_verify.html>

and the associated (downloadable) executable, FITS Viewer program that is available via the link on that same page.

If these utilities fail, then the problem does NOT lie with PixInsight.

HTH,

[Foton]

Thanks Niall,
Yes I've tried the verification tool with the following result:
 
              fitsverify 4.14 (CFITSIO V3.002)             
              --------------------------------             
 

1 Header-Data Units in this file.
 
=================== HDU 1: Primary Array ===================
 
*** Error:   Keyword #16, TEMP: String contains non-text characters.
*** Error:   Keyword #13, DATE-OBS: "" is not a string.
*** Error:   Keyword #13, DATE-OBS: (from CFITSIO error stack:)
             input date string has illegal format:
             
*** Error:   checking data fill: tried to move past end of file
 
   1 | SIMPLE  =                    T
   2 | BITPIX  =                   16
   3 | NAXIS   =                    2
   4 | NAXIS1  =                 1392
   5 | NAXIS2  =                 1024
   6 | BZERO   =                32768
   7 | BSCALE  =                    1
   8 | CAMERA  ='QHY2Pro Camera'
   9 | EXPTIME =             600.0000
  10 | GAIN    ='60%'
  11 | OFFSET  =                  119
  12 | TIMESYS ='UTC'
  13 | DATE-OBS='2009-03-21T00:06:39.515'
  14 | PIXXSIZE=                 6.50
  15 | PIXYSIZE=                 6.50
  16 | TEMP    ='-15.3°C'
  17 | END
 
 17 header keywords
 
 16-bit integer pixels,  2 axes (1392 x 1024),
 
++++++++++++++++++++++ Error Summary  ++++++++++++++++++++++
 
 HDU#  Name (version)       Type             Warnings  Errors
 1                          Primary Array    0         4     
 
**** Verification found 0 warning(s) and 4 error(s). ****

Obviously there are errors according to this tool, but I have to say that deep sky stacker has no problems reading the same file. I will raise the problem in the QHY forum. Any other suggestion is welcome.
Many thanks !. JLuis.

[Juan Conejero]

Hi José Luis,

Our policy is always to stop propagation of invalid FITS files, or FITS files that don't comply to the standard at least reasonably. The FITS format is enough problematic and is causing enough problems by itself; we really don't need the additional burden of incorrectly generated files.

Sorry for the inconveniences. I know you'll understand our policy. The people at QHY should be able to fix this issue ASAP. They must realize that format standards exist to be followed.

[Niall Saunders]

Of course, it IS possible to ignore errors and inconsistencies in the FITS HDU block - and some software packages do just that. It is also possible to 'ignore' the recommended specifications - and some software quite happily does that as well.

PI, on the other hand, adheres to the specification defined by the CFITSIO code, and WILL therefore reject image files that are non-compliant. And quite rightly so.

Perhaps you need to let your software developer see the results you posted here - any decent programmer should be greatful that an error has been detected and has been brought to their attention.

Let us know how you get on.

Cheers,

[Foton]

Thanks Niall and Juan. I understand your compatibility policy, no worries. Yes I've escalated the problem through the local QHY vendor in Spain, Lunatico. Will see if Tom (CCDSoft) has the same sensitivity. Otherwise I will consider swaping to another sw as I am very interested in using image integration utility in PI1.5.
Best. Jluis.