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 regularly stack +2000 images a session and run into the problem that sometimes in star analysis and further on again in Registration I get errors. No worries, I sort the list, then manually delete the few erroneous FITS and restart to finally integrate.
But is there no checkbox to automatically neglect the erroneous FITS files and continue the process? This question because running the analysis again means a loss of at least 2 hours per step and per session 🙁 Would be an immense help. Maybe the option is there, but didn't find it yet ...
Then the integration, I'm doing a 5 session one of 2500frames each (lights no spitted channels)
Calculations at integration consumes on average temporary 180MB*4 = nearly 1TB!
I'm writing the separate session raw integrations FITS, wo that's good.
I have now found back a 5the session (that I thought I had lost)
Question:
IF I process the 5th one and integrate this 5th session seperatly (not stretched or worked on ie step 6)
Then restart APP and load the 5 separate integrated session FITS (not stretched or worked on ie step 6) from APP
which would consume significantly less HDD space (only 5 separate processed session integration fits)
Would this give me the same result as reprocessing the 5 sessions completely (10.000 fits) into one final integration (integrate all)?
What is the recommended workflow for such cases?
thx
J
Hi Jan @janwalschap,
Thank you very much for your question.
Wow, that is a lot of images !!! Why do you stack so much? Do you use very short exposure times? If so, why? Why not expose a bit longer and get less images? I ask this, because if you can expose a bit longer, chances are good that the results will be better.
If each session is already 2500 images, than the result of integrating 5 session integrations of all 2500 frames will be the same as doing all together 12500 frames I would expect. The difference will be determined by outlier rejection performance and that will already perform very well wth 100 image, let alone 2500.
For me the recommend workflow is :
yes, create integrations first per session and then combine those sessions. And I would recommend to shoot far less frames but with longer exposure times if your setup allows it, things will be better for sure because the read noise will be more easily swamped in each exposure allowing you to go deeper.
Mabula
