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.
I have a fairly large set of files I am trying to integrate up using 1.082. Â There are 760 L, 149 R, 131 G, 108 B, and 376 Ha. Â All files register properly and no errors are generated when the integration runs. Â It takes a while given the large number of large files (camera is QHY600 which has 122 MB FITS files). Â I am running on Ubuntu 20.04 with 64 MB of RAM 56 MB of which is assigned to app. Â It is a Ryzen 8 core (16 processes - 15 assigned to app).
After the integration completes I have 4 beautiful integrated FITS: RGB and Ha but the L FITS is basically all white with three black horizontal lines one pixel wide. Â I was a little worried app might choke on so much data but there is nothing in the console to indicate a problem.
Is there a way to integrate in smaller batches and then register and integrate the integrated files?
That is a strange result, but yes you can chop the data in chunks. Which is what I would advise anyway when you have a lot of data. If each stack consists of something like 40-50 at least, all calibration should work fine and the resulting calibrated stack can then be combined later on with the other subsets.
Stacking into 7 sets of 110 each came out OK but when I tried to stack the subsets the gradients produced artifacts - I think because outlier rejection was behaving badly with only 7 images and cutting out some portions of the images as the gradients moved around due to meridian flips etc.
I was able to stack the majority of the images - I removed 60 and then another 60 subs based on the quality score and background levels and while 760 and 700 images didn't work once I got down to 640 subs it stacked fine without artifacts.
Ok interesting, that might indicate a data problem somehow as usually the gradients shouldn't pose that much of an issue (unless really super apparent).
