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.
Have a frustrating problem in 1.083.4 on Windows as follows:Â
I have a three-panel mosaic of the Orion region; stretching from M42 to the Horsehead, comprising of 5 sessions over 5 consecutive nights.
All the subs are identical across all panels: 300s of Hydrogen-alpha at gain139.
There is no difference in configuration, other than that for each panel the telescope is pointing to a slightly different region of the sky.
Everything calibrates as expected, and all subs on all three panels are of high quality.Â
Yet when I come to do Registration, APP fails to register the stars ONLY on the panel that happens to contain M42 (Orion Nebula).Â
Not just on one session, but for every independent session on every different night, APP fails to register the stars on that particular M42 panel.Â
After Analysis, APP even reports that the number of stars in the failed panel are about the same as the working ones (400-500) So it's not that it can't find them!
There is no reason I can fathom why that would be the case.Â
To have the problem persist on every consecutive attempt to image that arbitrary bit of sky, when everything around it works just fine, is mystifying.Â
There is no visible difference on this panel, and every sub has plenty of sharp, bright, and well-defined stars; just like all the other panels.Â
Any commentary or insight on this, before I get into the trouble of uploading 200+ FITS files? Â
Did you try with the latest beta version as well? If so and it still fails, I indeed do need the data to look at. I can start maybe with the panels which would not be that much data.
