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.
Hi Mabula,
Firstly, a big thumbs up for the new multi channel/session functionality - makes life a lot easier and I think improved results as well. I have an idea for another improvement which I will post separately.
Unfortunately I have had a problem this morning calibrating multichannels (HA, OII, SII) over four sessions with Lights, Darks, Flats, Dark Flats and Bias frames.
The calibration ran to 90% and then just stopped, oddly APP has not completely crashed, I can still scroll the main and console windows and CFG/Info still open, however the Cancel button doesn't work.
I have plenty of storage, SSD for C: and a Samsung T1 SSD for the APP Directory on Windows 10 with 6GB RAM allocated. In case its of relevance I loaded the wrong Dark flights for one set of lights and "Removed" them and loaded the correct ones. Other than that I don't think I changed any defaults, just ticked the generate BPM button and then "Create Masters....".
It took a long time to load and check everything so I am a bit reluctant to try again and would be grateful if you could take a look. Let me know if there is any other information required (perhaps a log somewhere?). I have attached a screen print that shows the stage of processing when the freeze occurred.
Thanks
Jon
PS For information, the APP site is running very slowly today.
Thank you @midnight_lightning,
The provided information in the console and the calibration process is enough to know where it is stalling now. I will have a look immediately to solve this.
Mabula
Hi Mabula,
I may have found the issue.
I have been trying different things since originally posting and noticed that the Lights from Session 1 frame IC1805 quite differently to Session 2-4. In Session 1 there is perhaps 10% to 20% difference in overlap compared to the other sessions. This is data from last year that I am reprocessing and I had forgotten that I messed up the framing on the first session.
So, I don't know for sure whether this caused the issue but I have rerun the calibration using data from sessions 2 to 4 and it worked fine.
Apologies if this is user error, I don't want to be wasting your time.
Jon
Â
No problem, I have investigated and I think it's not related to the amount of overlap between the frames 😉 but rather a concurrency issue between several threads. In almost all cases, the calibration process finishes like it should, but apparently, sometimes not. I need to do some more tests, but I think I have located the source problem 😉
Thanks,
Mabula
