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.
To borrow from Maxwell Smart, I got THAT close! Just 10% more to finish integration of my 406 frames. I did get masters for the individual sessions. I had allocated APP 32 gigs, but not quite enough. I upped it to 48 gigs but had to shut down to access it and restart but all the in-memory stuff appears to be gone. What do I have to do to resume?
You mean you got masters for the calibration frames? Well that's a start. Are you using virtual memory? It probably should work, but I'm not very confident on that, how's APP handling that @mabula-admin ?
I have 64 GB actual memory. I reserved 32GB for APP, and I didn't notice it was approaching that until too late. I'd like a way to recover more gracefully. 🙂Â
I had it set up to integrate by filter and total. I got the by filter masters, it crashed when integrating all 406 subs. Kinda crazy to do that, but just wanted to see what happened. I'm thinking of reducing the Lights to be Integrated to 80%, believing it will then not use the lower 20% quality?
I like crazy processing to be honest, it is something APP should handle gracefully of course, so if it doesn't that might need a bit of attention.
Yes, I actually always do that, when collecting data I already tell SGP to dismiss any frame with a certain guiding error and then integrate like 80-90% (based on the total amount), resulting in the best frames to integrate. No need to go through them by eye then really. Do select to integrate based on quality.
