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.
FAQ - Frequently Asked Questions
1
Posts
1
Users
0
Reactions
1,473
Views
Topic starter
April 26, 2024 07:49
Hi Team, say I have data for the same object from three or four different camera/telescope systems. I know that APP makes it trivially easy to combine the data, but how does that combination actually happen? By that I mean, what's the actual process for determine which pixels to use from which sources? Say I'm combining data from a Celestron RASA 8" and a 2 megapixel camera, with data from a Planewave CDK 20" and a 64 megapixel camera. Will my final image resolution be closer to the former, or the latter, assuming equal number of frames?
