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.
Hi APP team,
Query.
I have a session of files that I previously calibrated and aligned channels using APP. They are now fully debayered and calibrated fits files.
In another session, I have yet to process, so they are as-acquired fits files together with their calibration frames. I am not going to align the channels on this second session.
Can I load the calibrated, debayered files as session 1, and also add session 2 with fits files + calibration frames and stack together? I assume no issue as they are treated separately before being integrated?
Â
Thanks, Colm
That should be possible yes, or if you want to make it even simpler, just process the other session on its own, then load that integration together with the first.
@vincent-mod
Thanks Vincent. One of them is APO data, different optics, so I was hoping to be able to integrate all together for good rejection, LNC etc., also because of different moonshine levels. The framing is almost 60 degree rotated between the two scope so I will probable need flip descriptors also. Not sure if I should use mosaic registration though? I will try integrating all subs together first as session 1 and 2 and see how it goes.
Well yes that may help, if you have enough data for that one session though it shouldn't make a big difference. But doing it like this should be fine. Don't use mosaic settings for a similar FOV, a mosaic really means panels that have no overlap whatsoever basically.
