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 am having memory exhaustion issues when working with larger mosaic projects, and hoping for some guidance.
My most recent project is a mosaic of NGC1499. Currently I have two images being combined into a color image and I get errors about not enough memory to complete the combination. I have a Ha sub and S2 sub, each have the following:
- 1345MB file size
- 19046 x 18514 pixels
- FITS format
These subs have been processed using APP separately. I actually ran into memory problems when trying to normalize and integrate the final images to get proper alignment, and had to increase my memory allocation to 20GB in APP.
When I load up the two images in the combine RGB tool, it takes 8512MB just to load them. Doing recalculates continue to raise the memory taken until I eventually run out (almost as if memory is not freed up with each action). I have had to close APP and redo the combining with each recalc, and have also tried to crop down the images to make the file size smaller. This has allowed me to at least get a combined image saved, yet I cannot tweak the image in APP to my liking due to these issues.
Looking for any advice on how to get APP to allow me to work with larger images, especially as I have upcoming project data sets that will even be larger. Is this something I can configure in the application? Do I simply need to get more RAM for my machine? I can go up to 64GB of RAM if that is even enough.
Machine specs:
- Windows 10 (vers 2004)
- Ryzen 7 2700X
- 32GB RAM
Thanks!
While we wait for @mabula-admin, it's also clear that that resolution is very high. So that indeed requires a lot of memory just to load them, I think it might be necessary to downsize that a bit (though I understand that's not preferred). You can do this in tab 4 "register" and register everything, then setting the scale to 0.5 for instance and save those frames. Just to try to get this to work with the amount of memory.
I am having memory exhaustion issues when working with larger mosaic projects, and hoping for some guidance.
My most recent project is a mosaic of NGC1499. Currently I have two images being combined into a color image and I get errors about not enough memory to complete the combination. I have a Ha sub and S2 sub, each have the following:
- 1345MB file size
- 19046 x 18514 pixels
- FITS format
These subs have been processed using APP separately. I actually ran into memory problems when trying to normalize and integrate the final images to get proper alignment, and had to increase my memory allocation to 20GB in APP.
When I load up the two images in the combine RGB tool, it takes 8512MB just to load them. Doing recalculates continue to raise the memory taken until I eventually run out (almost as if memory is not freed up with each action). I have had to close APP and redo the combining with each recalc, and have also tried to crop down the images to make the file size smaller. This has allowed me to at least get a combined image saved, yet I cannot tweak the image in APP to my liking due to these issues.
Looking for any advice on how to get APP to allow me to work with larger images, especially as I have upcoming project data sets that will even be larger. Is this something I can configure in the application? Do I simply need to get more RAM for my machine? I can go up to 64GB of RAM if that is even enough.
Machine specs:
- Windows 10 (vers 2004)
- Ryzen 7 2700X
- 32GB RAM
Thanks!
Dear Sean @realwizer,
Okay, I think I understand what you are trying to do.
It sounds like there might be a memory leak in the Combine RGB Tool that causes the needed memory te get expanded after each recalculate. I have put this on my ToDo to test. Right now I am not aware of such a problem, so I need to test this. I will try to do this before releasing the next version.
What I would suggest as well, is that to make the mosaic for the 2 different filters, that you create them at the same time using the mosaic mode in Multi-Channel mode, that will make sure that both the Ha and S2 mosaic will be aligned and normalised straight away 😉
If you plan on making even larger mosaics, then you definitely need more RAM yes.
I hav created large mosaics of roughly 20.000x20.000 pixels in RGB in the past with 32GB of RAM, so I do think that you are confronted by a memory leak/issue in the RGB Combine tool that is preventing you from completing the image now. Hopefully I can find the cause and fix it for the next release 😉
Mabula
Ok, thank you all for the replies.
I will plan up getting the extra 32GB of RAM since I have 2 slots open. Again as I plan to go even larger this may help.
Regarding any leaks, if they exist, let me know if you need anything else from me to narrow this down. And in the meantime I will normalize as suggested.
Greetings!
Was this issue of a "memory leak" in the RGB Combine Tool ever established as the issue? Here I am closing on 4 years later, with a very similar issue when trying to use the Combine RGB tool. If it was addressed as an issue that we the users need to attend to, would someone please direct me to that explanation. I am currently using Version 2.0.0 beta 28!
