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.
Should I wait for integration to finish or it's already "done" after this exception?
Hi Maxim @mseningmail-com,
I have never seen this exception earlier. The LNC algorithm in beta4 is identical to 1.083 stable, so it is very likely that the LNC calculation can not complete due to some problem.
For beta5 probably and definitely 2.0.0 stable, a new LNC algorithm is being developed which must be better, faster and use less RAM. It will be LNC 2.0 🙂 I am working in this at the moment.
So for now I would suggest you tro try LNC 2nd degree and let me know if that does complete on your data. Maybe if it also fails, it will be good if you share your data so I can test it for LNC 2.0 as well 😉
I think the error prevents the stack from completing unfortunately... I will also fix that going forward.
Mabula
Hi Maxim @mseningmail-com ,Â
After the Java exception there is no point in waiting. If I am not mistaken, You'll need to quit and restart APP again.
LNC works for me up to 6th degree (I did not yet try more, though).
But LNC is highly depending on CPU single core speed as well as  SSD & bus speeds and RAM size.
Depending on Your computer it might be more or less. 2nd degree should work though and already provide nice results using 3 iterations.
Hi @Mabula-Admin
looking forward to LNC 2.0! - once this works on multi-core code it might scale by a factor of 3 or more...Â
Â
Thanks. Looking forward to the new version!
I can only add that this happened with 2 sessions of NB data from same optical train, when I chose "Integrate - per session and all", and to apply L4 LNC with 3 iterations on individual session stacks and final stack. And reproduced it again on 2-session stack where images were from two different optical trains. All same settings except for registration (dynamic distortion I unchecked "same optics" and checked "flip descriptors X/Y" and increased scale stop to 15. Both cases drizzle 2.0. IDK if that helps anyhow.
Hi Mabula, glad to hear you were working on LNC 2.0. Is it possible to process very large stacks, say over 1000 frames and more, with the new version? With large stacks I always get the message Can,t get Sample Size and LNC was not applied.
With best regards.
Another exception in 4th degree LNC processing 2-session stack. Different this time:
