UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
Hello, for info, with 2.0.0.Beta26, I got this error after processing 6 other image series without problem. I shut down and restarted the program wich gave the same error on the same image set. I'm processing series of only 10 images each, in this case M45. I then loaded and processed four other image sets without restarting the program and this worked well. Processing is with master-dark, master-flat, master-dark-flat and BPM. I then reloaded the M45 set and viewed each image in the viewer. One image of the 10 could not displayed, I removed this frame from the set and then the processing went well in the end.
Edit By Mabula: solved in 2.0.0-beta29
Hi Geert @geertvdbulcke,
Thank you very much for reporting this. This issue was reported by another user as well and we are investigating it. Can you reproduce the issue with certain data? Can you upload that data here:
https://upload.astropixelprocessor.com/
username: uploadData
password: uploadTestData
Please make a folder with your name and issue like: Geert-SixteenBitsConverter-issue
and upload there and let me know once done, thanks !
Mabula
The error was caused by one image FITS file taken with MaximDL 6 and my QHY268C. One file of 10 probably had a write error as it could not be opened with MaximDL either. I don't have that file anymore.
Groetjes,
Â
Geert
Hi Geert,
Yes thank you, I already suspected that it concerned corrupt fits files...
I have now build in a proper detection of this issue and the user will be warned that a certain file seems to be corrupt.
Thanks,
Mabula
