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.
Topic starter
July 24, 2018 23:15
Hi Mabula
I processed some data tonight and checked the Bad Pixel Map creation box (too lazy to select an existing one for the camera!). I had checked multi-channel/filter processing, but not multi-session. During the calibration process, I had error messages asking me to select the BPM for each Light frame. It gave me a choice of 5, but it refused to use any of these, saying that the instrument name of the BPM did not match that of the Light frame (42 in total). When I checked, sure enough, it had made 5 BPM files:
I will try this data again tomorrow, using an existing BPM and see if that is accepted.
Thanks and regards
Dave
This topic was modified 8 years ago by Jonesdee
