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.
I have imaged the Cat's Eye Nebula in two consecutive nights using the same setup with a ZWO ASI294MC Pro one-shot color camera and the Optolong L-Extreme filter. If I stack the data from the first night, the results are as expected. The results from the second night show a strange color cast when I process them even when using only the standard settings and hitting "integrate" right way:
In the first night, I imaged at -10°C - the second night at -20°C for 300s per sub. Individual subs look like this:
Flats-, Darks- and Bias-Frames don't show a visible difference (except less noise @-20°C).
I have tried both, the Adaptive Airy Disk and the Ha-OIII color algorithm - both with the same strange result for the second night's data.
The normalization map files do differ significantly:
Other targets imaged the second night look fine and can be processed without problems.
Did someone see this behavior before and has an idea, how to deal with this?
Thanks for any suggestions!
Phillip
