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
I'm trying to process some data I've taken over the last couple of nights, it's a mosaic, I've selected the options APP wants as it's a mosaic and I've also got drizzle of 0.5 droplets and 2x scaling. The result of my Ha and OIII frames correctly build and I get the fits file at the end. My SII reliably gets an exception trying to write the fits file right at the very end. I've got nearly 900GB of free disk space, so it's got room. I've restarted APP and tried to process just the SII and it still does the same thing. The error message just says an exception occured, with no detail as to what exception, so I have no way to try and correct the problem. The console doesn't have much more information either (other than the last message before failure being "creating FITS HEADER...").
Any way to get any extra logging information so I can try and see what's going wrong?
Thanks
I upped the RAM that APP can use from 48 to 56GB (out of 64) and it seems to have progressed.
Mm, that still shouldn't just throw an exception I think, did it work out in the end though?
