Some FIT files not opening after latest version update

[RATTLER]

Hi guys. I installed the latest version yesterday. I am having issues opening some but not all FITS files. It seems that files I have previously used will open but new ones wont..odd. I have sent the file to someone who hadn't updated yet. It opened in the previous version but not in the latest. I have also moved the file to another location to ensure that it wasnt saved in corrupt storage. Anyone else have this issue or any ideas? Cheers

[Juan Conejero]

Hi. This looks like a bug in CFITSIO (the software library we use to support FITS in PixInsight). Can you please upload one of these FITS images that is causing this problem, for example to Dropbox or something similar? Thank you!

[RATTLER]

Thanks Juan. Here's the link to the fits file.

https://app.box.com/s/z24v0cqao4t2jfa66py9drf7t99azmdm

[Juan Conejero]

Thank you for uploading this file. The checksums declared in the FITS header (CHECKSUM and DATASUM keywords) are not valid, that is, they don't correspond to the actual data stored in the file. Assuming that the original checksums were computed correctly in the first place, this means that the file has been tampered with since it was created. See the FITS verifier report:

Code: [Select]

File name:  1.fits
                                           Run Number 23945
 
              fitsverify 4.18 (CFITSIO V3.440)             
              --------------------------------             
 

1 Header-Data Units in this file.
 
=================== HDU 1: Primary Array ===================
 
*** Warning: Data checksum is not consistent with  the DATASUM keyword
*** Warning: HDU checksum is not in agreement with CHECKSUM.
The problem is that this FITS file has been compressed (using the dithered pixel quantization method, which means that the data have been 'scientifically' destroyed, but that's a different story ). The changes made to the compressed data seem to render them unmanageable for the latest version 3.450 of CFITSIO, which is used in PixInsight 1.8.6. I'll see if reverting it back to 3.440 fixes this problem. Sorry for the inconvenience.

[RATTLER]

Hi Juan. Any update? Cheers.

[RATTLER]

These files stack fine in other software.

[RATTLER]

Hi Juan. Is there any update on this yet? Not heard anything for a while.

[Juan Conejero]

This bug is now fixed in the next version of the FITS support module, which will be released very soon, along with a new version of PixInsight. To be fair, the bug was in my code, not in CFITSIO. It has been difficult to find but this problem is now solved.

Sorry for the inconvenience, and thank you for your patience.

[Phillip Klein]

Hello,
When I open Fits files PixInsight says the files are depracated. The files were created in SGP. I am unsure what the message means and what I should do to avoid using "depracated" files in PI.
I appreciate any advice you can provide
Thank you

[pfile]

in the software world a "depreciated" feature usually means that the feature is no longer maintained, and could be removed from the software in the future.

in this particular case, juan is saying that the XISF format (which is a superset of the fits format in that it supports fits keywords) is the new default file format for PI and should be used instead of fits. since fits is never going to go away, it's unlikely that PI would ever remove support for fits. and if there is some bug in the cfitsio library i'm sure juan would roll in any fixes if necessary, again since fits will probably never go away.

rob

[Phillip Klein]

Hi Rob,

I appreciate your reply.

Would you recommend I save the Fits file in XISF format prior to processing the files in PI. I do not believe I can change Sequence Generator Pro to save the subs in XISF format.

Thank you,

Phil

[pfile]

you are right, SGP can only save FITS files. since PI writes XISF by default, when you calibrate your fits files or run BPP, the calibrated/registered frames will be saved as XISF automatically. you don't need to explicitly convert the subs from FITS to XISF.

rob

[Phillip Klein]

Rob,

Thank you for the great information. I sincerely appreciate your time.

Thank you again,

Phil