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
November 12, 2018 21:03
I guess I'm not sure what Multi-Session processing is needed for? For example, if I shoot subexposures with different binning, should I treat those as a different session so I can apply different calibration frames?
Thanks
Wayne
November 20, 2018 23:51
Uhmmm good question. 🙂 Multi-session is usually done for, indeed, having different calibration frames to be assigned to different sessions. Why would you use variable binning during 1 session if I may ask? I guess you simply can use the multi-session for that, but I don't think it's a usual workflow.
Topic starter
November 25, 2018 23:17
Come to think of it, I probably wouldn’t assign different bins to the same channel. I might though bin S2 and O3 2x2 and Ha 1x1, but I guess that doesn’t require different sessions
