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.
If you change out one of your calibration files, like a flat file, after star analysis, registration and normalization is done, why is it that APP start over from scratch doing all these steps over again?
In what way is a flat file (or any calibration file) used for star analysis and registration? 🙄Â
Not sure, I never actually tested that, why would you want to change a calibration file during the process and after everything is calibrated?
This was actually a curiosity question and not a big deal, but what happened was that my integrations looked like crap. I realized that I had used the wrong flats. I should of course have checked that up front. So I thought I could just replace them and rerun the integration (and possibly normalization), but no such luck. APP started doing star analysis. That, and registration, take a couple of hours with a lagre stack.Â
So maybe you could ask Mabula why it is like that. There is probably a good reason. I'm just curious.Â
Oh yes, didn't mean to say it isn't interesting. 🙂 We discover bugs sometimes precisely because people use the program slightly differently. The next version of APP will have the ability to skip steps, so if you save, for instance, the star registered frames, you can load them in later again and tell APP to skip star analysis. This may not fix this particular situation though, so if that remains to be the case please let us know and we will fix it.
I did a little testing just now to see if I could recreate what happened. 20lights, one of each type master calibration files. First I did a full integration using all standard settings.
There seem to be three scenario:
1. Adding a new flat and unchecking the other, press integrate and APP start integration as expected. (But I'm not sure which flat is actually used)
2. Delete the existing flat (using clean) and then add a new one. Press integrate and APP starts with registration then normalization and integrate. (Here I belive the new flat is used.)
3. Delete the existing flat (using clean) and then add a new one. Then press "reassign masters to lights". All existing analysis are deleted and APP starts with analysing stars.Â
There is probably good reasons for all of this, but if there isn't......Â
