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
One thing has been annoying me for quite some time:
If one file fails to register, the whole process stops. Why?
Why can't the process just continue with the files that did register? You can always go back and re-register (start over) if you want to include that file.
Several times I have experienced that I start a process including several hundred files which I know will take hours, but when I get back to the PC the darn thing has stopped . This is not user friendly!
Display a message on the screen, but please, pretty please, let the process continue with the registered files.
Hi Heno,
Yes this is indeed the case and something Mabula will change, good point.
Hello,
I second what Heno has said. It's discouraging to set the computer to process overnight a large batch of files, and then discover in the morning it didn't go because a few files failed register.
I just had a multi session fail, which consisted of data of the same subject using the same equipment over 5 nights. Lights from each night's session were previously calibrated, saved as calibrated lights, and successfully registered and integrated within each session. When I then went to integrate all the calibrated lights from the 5 sessions into one master integration, 12 of the 600 or so calibrated lights failed to register. Now, the reason I had integrated the individual sessions was to make sure that I had good lights that would register (because I have had this problem before). So I was surprised that when going to a big multi session a few of the known 'good' calibrated lights failed to register under this circumstance.
But regardless of the reason these calibrated lights failed to register in a different integration, I just want the system to continue the integration process without the lights that failed to register. A warning message that a few light frames failed to register and therefore were not included in the integration is sufficient. Thank you!
P.S. I want to say that overall I am quite enjoying APP!
