2022-05-11: APP 2.0.0-beta 1 has been released !!!
Download links per platform:
Invalid FITS Header on ZWO ASI 178MC
I have actually just run in to this problem with a few .fit files shot using Voyager and a QSI6162 camera. I tried using the current beta but that still threw an invalid fits header error. Is the workaround that was based on the ASI cameras fully implemented in the current beta 1? Can I send a file via wetransfer or similar? The output of the 6162 is 30.9 meg so I can't attach a sample file to examine here.
Incidentally, I have always used an ASI camera with Voyager (First an ASI294MC Pro and now an ASI2600MC Pro) without ever seeing this error, it must be specific to particular cameras or drivers.
I just realised that I think I have misread release notes for 1.83 beta 2 as applying to beta 1. If that is the case I will wait with bated breath for the beta 2 release, hopefully in the coming days.
@the_bluester Yes there will be better handling of some types of corrupt FITS files in 1.083 beta 2. If you want to know if your files can be opened with that version then please upload a few files to
using upload5 for both username and password. Please create a directory called the_bluester_corrupt_fits and place the files there. As soon as the files are there I will ask Mabula to have a look at them.
Thanks, I have uploaded two, even one would probably do. My friend is considering a move to Voyager so it would be good to know up front that 1.083 will open files produced by it from his camera.
Yes, APP 1.083-beta2 has the fix for this problem:
WORK-AROUND IN FITS READER, FOR APPLICATIONS THAT USE A FAULTY FITS WRITER: some users reported problems with some FITS files where APP could not read these, but other applications could. The topic is : https://www.astropixelprocessor.com/community/camerasupport/invalid-fits-header-on-zwo-asi-178mc/ Some of the problem FITS files come from the Voyager capture software developed by Leonardo Orazi. Together with Leonardo, we have found the root cause of the problem. It turned out that the FITS writer code that is used in Voyager is a badly ported version of the nasa java fits library that we use in Astro Pixel Processor. The ported version is not following the FITS specification for how the FITS Header bytes should be filled with byte values once all metadata has been stored. So the root cause is not in APP, the root cause of the problem is in the capture software or the ascom driver that such a capture package uses. Leonardo has fixed this issue in Voyager and in APP, I have implemented a work-around so that this particular FITS issue is detected and the files are still read properly.
So the error actually is in older Voyager versions and other applications that use a faulty fits writer. Leonardo Orazi from Voyager has solved this issue form his end as well 😉 And APP 1.083 will be able to read these problem files as well.
To be sure, I have just checked your uploaded files in APP 1.083-beta2 and yes they work fine now 😉
Thank you for checking. I will have to follow up with Leo, the version I was using is pretty up to date, it might be a separate problem if the fix has been implemented already. It might be a while before I can test again, we were supposed to have another go tonight but we both live in Victoria (Australia) and are under a COVID lockdown at the moment so that is not going to happen.
Regardless of that, it will be no problem in the future given 1.083 will open the files anyway, looking forward to the beta 2 release.