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.
The error mentioned above occurs in APP 1.059 while trying to integrate H-alpha DSLR subs. It occurs with everything on default settings, but also when settings under 3) Analyse stars, 4) Register, 5) Normalize are changed. Also doesn't seem to matter if algorithm under 0) RAW/FITS is set to H-alpha or Adaptive Airy Disc. The lights are calibrated with a master flat and master bias. All @ ISO 1600.
Â
Enabling bayer drizzle seems to cause the issue... I'm further investigating the problem.
Hi @maurice_toet,
What happens if you alter the drizzle droplet size and integration scale? Do you get the same error?
The progress indicator is only at 10% so it seems to occur when the first frame of the stack is loaded. Perhaps it is usefull if you could send me one of the frames and the calibration masters, or 1 or 2 calibrated frames. Then I can probably quickly find the root cause 😉 of this...
Kind regards,
Mabula
Yes, Bayer Drizzle causes the issue. Quite obvious coming to think of it...
Hi @maurice_toet,
What happens if you alter the drizzle droplet size and integration scale? Do you get the same error?
The progress indicator is only at 10% so it seems to occur when the first frame of the stack is loaded. Perhaps it is usefull if you could send me one of the frames and the calibration masters, or 1 or 2 calibrated frames. Then I can probably quickly find the root cause 😉 of this...
Kind regards,
Mabula
I missed your post. I'll send you some files so you can have a second look.
Hi Maurice @maurice_toet,
I have found the bug... it was a combination of applying bayer drizzle and DSLR data with raw borders. In normalization, the datatype is changed to 32bits floats and the raw borders of the DLSR data weren't dealt with properly for Bayer Drizzle, causing the bug...
So this will be fixed in APP 1.060, soon to be released.
I assume you were able to create a good integration with either regular integration or Drizzle integration using the H-alpha debayer algorithm?
Cheers,
Mabula
