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.
Last night I ran APP 1.074.1 on my data. This morning I looked at the result and this exception popped up:
Steps 0-6 were finished and didn't have any issues. I was opening the integration result image and used the DDP dropdown menu to switch between stretched previews. If I remember correctly I was opening a different image while the DDP change was still loading in the background (or vice versa).
My guess would be that this is a concurrency issue. I could not reproduce it, but an extra null check never hurts 😉
If you need more information let me know. The log didn't contain anything useful concerning the issue, so I hope the (rather minor) stacktrace will be enough.
Last night I ran APP 1.074.1 on my data. This morning I looked at the result and this exception popped up:
Steps 0-6 were finished and didn't have any issues. I was opening the integration result image and used the DDP dropdown menu to switch between stretched previews. If I remember correctly I was opening a different image while the DDP change was still loading in the background (or vice versa).
My guess would be that this is a concurrency issue. I could not reproduce it, but an extra null check never hurts 😉
