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'm running out of RAM when integrating large data sets. I have an F/2 imaging system so my exposures are short. I have 16GB of RAM but can't integrate more than 300 or so frames from my ASI183MM. I have several data sets with 600-1000 frames.
Is there anything I can do to integrate this data? Would I loose anything by doing 250 frames at a time and the integrating the resulting integrations based on exposure length?Â
Could APP warn me before I spend 3 hours integrating data just for it to die at the end? Could SWAP space be used on my SSD instead of just dying?
Â
-Jim
I had the same issue processing a large data set of 1000+ images. I have 32 GB RAM and had to max it in APP in order to get it to go through. But I actually made several attempts increasing it a few megs here and there, until I got tired of waiting 5 hours for it to process only to find out there was not enough RAM.
When integrating so many frames, it's better to divide the frames into sub stacks of say 200 and combine those later.
ps. Mabula is also aware of this issue, it seems to be a problem when using LNC. Did you have that on?
