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 get this message. I'm running 19 treads of 20 on I9 cpu. Win11
Â
Dear Gustav @glundby,
Thank you very much for reporting this bug. I will have a look in our code using the error message to try and understand what is happening here.
Is this error always happening on a certain image or set of images? Can you upload those images here so I can test and fix this as soon as possible?
https://upload.astropixelprocessor.com/
username: uploadData
password: uploadTestData
Please make a folder with your name and issue like: Gustav-ArrayIndexOutOfBounds-SumSignal-bug
and upload the data there and let me know once uploaded. I will test and fix it as soon as possible.
Mabula
Dear @glundby,
Is this issue still there? If so, can you upload the data as instructed above, so I can test it? Thanks
Mabula
Sorry!
Do not have data now but it happened two times with different data sets. both with two sessions, same camera... Full format and fairly big amount of one shot color subs. Typically when each session where processed by it self, it did not happen. I have I9 - gen 13 using 19 treads and have 32GB memory. About 750GB free disk. Next time it happens (need clear skies!) I will try to collect data. The data sets will be huge however!!!
The bug happens each time about same place in data set as far as I could notice. Looking at the log stream I could not see any unusual messages.
Testing big two session dataset... Sorry! could not recreate error!
Regards! Gustav Olav Lundby
Hi Gustav @glundby,
Okay, thank you very much for the feedback. So the 2 sessions would create it, then maybe I can understand why the issue happens. Could it be that 1 session is RGB and the other session is monochrome perhaps?
Mabula
Hi!
No! I got the error again now! Simple straight forward single session with about 320 subs - 6.1Gb data. It happened after about 60% of the subs in 5 Normalize. When the requestor comes up I cannot get rid of it and cannot move windows to look at log window. Is there any logfil I can find? I think I enabled log last time??? I have captured the window; but need help to find more information.
Regards! Gustav Olav Lundby
Â
Hi Gustav @glundby,
Thank you very much for reporting this. Okay can you upload your dataset on which this happens here:
https://upload.astropixelprocessor.com/
username: uploadData
password: uploadTestData
and make a folder with your name and issue: Gustav-Error-SumSignalInCrop
and upload your data there and let me know once uploaded, then I will look at it as soon as possible.
Does this error on this dataset happen each time that you run it? Or will it only happens sometimes?
Mabula
Hi Gustav @glundby,
Allthough i haven't seen your data and do not fully understand your error, I have made code adjustments to prevent this issue from occuring again. The fix will be in the next release 2.0.0-beta35.
- FIXED ArrayIndexOutOfBounds exception in SumSignalInCropWorker
As reported here, https://www.astropixelprocessor.com/community/rfcs-request-for-changes/low-level-bug/#post-32300 , in some rare occasions an ArrayIndexOutOfBounds exception could be thrown in the SumSignalInCropWorker causing a problem to continue processing in APP. This error should be fixed now, and processing should continue automatically.
I have a final question though: could it be that you are running several instances of APP at the same time? If so, maybe that explains the issue, because APP is not specifically designed to do that. If not, then this issue is still not very well understood yet and I have never been able to reproduce it yet.
Mabula
Â
