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,
I'm currently trying to stack my first light images (Skywatcher Evostar 72ED) of M13. I have 100 lights and 30 darks and bias frames. The image quality is not very good due to the fact that I still waiting for my field flattener to arrive. To get something out of my images I only stack 70 out of 100 light frames but during the normalization process all 100 frames are processed. Why is this done if only 70 of them are used at the end? The quality score of an image is calculated during the calibration in step 2 so it is already there when the normalization process (step 5) starts and at the end (step 6) only 70 of my images are used for integration.Â
For me it could have saved 30% of the time the normalization step took saving about 15 minutes or so.Â
Maybe somebody could bring some light into this.
With best regards,
Mario.
The quality score does change when subsequent steps are processed, when APP knows more about the data because of those steps, things can change.
