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,
I was processing a set of LRGB subs yesterday evening and encountered an odd result in the L channel. R, G and B all look OK.
Â
While checking my input L subs I observe an issue with a few (c10-15Â of 58) of them, when changing the viewer mode from 'l-c-registered' to 'l-c-r-normalised', so I suspect something is going amiss during Normalisation.
L-C-Registered:
L-C-R-Normalised:
I have processed c60% of the input subs previously without issue but managed to grab a few more during a recent clear night.  The calibration frame have all been used previously with other images without issue. I ran the integration a second time with the same result. Prior to starting this integration, I had done another target without issue and had simply cleared the previous subs and changed the working directory before starting NGC4244.Â
I plan shortly to re-boot my lap-top and do a further rerun to see if the issue is still present. Â
Could you check the offset you used for the subs and the calibration data?
Hi Vincent,
Having rebooted and restarted APP the integration the results now look as expected.Â
I have no idea why it was only the L channel that had this odd result, or why it seemed to be only a small number of L subs that displayed very high contrast when switched to L-C-R-Normalised mode.
I guess there must have been some sort of initialisation or other transient issue as a result of switching targets without first restarting APP.
I have a CCD camera so offset is not something that I can set.
Regards
Mike
