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.
When stacking a mosaic if I let the app use the highest Quality Score image as the reference frame the registration in part of the image is bad. If I instead tell it to use the lowest Quality Score image the registration is fine (although the color is off). I have several panels I am combining so I was able to try different combinations and the results were the same. Changing the reference frame changes the ability to register. Is this expected behavior?
I batch cropped the 2 results:
Hi Steven, @mrrat
That is not expected behaviour, the reference chosen does determing hope APP will calculate the mosaic. In this case I would suspect that the calculation is slightly more difficult somehow. Maybe a tweak of the registration parameters will solve it, or increase the number of stars a little bit in 3) 😉
Mabula
