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.
My system is just hanging trying to calibrate the BPM - see image. It seems to have created all of the Master files before crashing and is non-responsive to "cancel"
This is a 2 session integration:
- Session 1 is straight RGB - 1x1 @300sec.
- Session 2 is LRGB with LÂ 1x1 @900sec and RGB at 2x2 @300sec.
For calibration I have
- Flats and Dark Flats for each set of lights
- Darks for 1x1 and 2x2
- A Bias file for each session
Any thoughts?
Thanks
Jon
Apologies, I posted this in the wrong section but don't seem to be able to move it.
I've had a similar problem. APP hangs at 90% when creating a new BPM. When I removed the request for a new BPM and used an old one everything worked ok. I was going to report this when I could isolate the actual conditions that caused it. However, I haven't been able to reproduce the problem but decided to post this information when I saw midnight_lightning's post. I know it occurred using multi session and multi channel. I kept more detail, including screen shots. However, I'm away from home for a week or so but will send them to you when I return.
Hi Jon @midnight_lightning and Tim @tim,
This is with APP 1.062 right?
I will have a close look at the module that is creating the final bad pixel map, in this case, it seems to wait for something before finalizing. I should be able to find the source of this issue.
Does it always occur if you follow the same routine?
Mabula
Â
Hi, it's happened a couple of times but doesn't always happen, I haven't worked out what scenarios cause it so far - sorry.Â
Hi Jon @midnight_lightning,
I have corrected the code and thank you very much for bringing this to my attention.
The issue was a synchronization issue in a multi-threaded environment. The code has been adjusted and is now threadsafe. Issues like this are a bit complicated, since they only manifest themselves sometimes.
I will release APP 1.063 with this fix now as soon as possible 😉
Kind regards,
Mabula
Â
Hi Jon @midnight_lightning,
I have corrected the code and thank you very much for bringing this to my attention.
The issue was a synchronization issue in a multi-threaded environment. The code has been adjusted and is now threadsafe. Issues like this are a bit complicated, since they only manifest themselves sometimes.
I will release APP 1.063 with this fix now as soon as possible 😉
Kind regards,
Mabula
Â
And for Tim as well @tim,
I have fixed this problem and will release APP 1.063 with the fix as soon as possible.
Mabula
Thanks Mabula, looking forwards to processing these sessions again. 🙂
Â
