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.
Ive been using APP for a few years now, but never ran into this particular issue until tonight. Long story short, I have ~13 hours of Ha data which I acquired over a span of roughly a week (with 4 clear evenings). The subs generally look good, and an initial test stack looked completely acceptable. However, I want to go back and weed out ~30 or so subs which were taken in the early evening when my target was low in the sky. I usually do this by plotting the sky background value in a line chart, but for whatever reason my line chart looks like this. Am I just being a big dope and doing something dumb? Thanks in advance!
I would keep them if they look good and the background light isn't enough to mess anything up. Just think of it as shooting Ha with the moon out as an equivalent.
