Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
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
Â
