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 guys...
I got this error message when processing some one-color-shots of IC342 today:
 Any idea what might cause this? Never happened before, running APP v.1.083 beta2.
best
AJ
@ajnilsen Can you tell a bit more about the data you're processing? How many lights and what calibration data did you use? Does the problem happen again if you stop and restart APP or if you reboot the computer?
Hi...
I uploaded 101 lights, one masterdark, one master bias and oine master flat as well as one BPM. It happens when I restarted the PC also as well as when I restarted the program. However, when I removed the master bias, it seems to work, so the error might be caused by a corrupt master bias frame. I'll continue to investigate and shall let you know...
Thanks!
AJ
Â
No, it was created with an earlier version....
AJ
@ajnilsen Depending on how old the earlier version was, that may have been the cause. I'd advice you to take new bias frames and create a new master. If you cannot take new bias frames and still have the old one, please create a new master bias from those.
Hi...
I took a series of new bias frames and generated masterbias using APP v. 1.087beta. This solved the problem :). Thanks!
AJ