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.
I am on 1.067. I always just use default settings except for 6). Got a message that APP could not detects stars and that I had to lower kappa value. in 3). I then started playing around with the values but with no success. Could it be calibration data that perhaps need to be redone?
My humble apologies. APP works perfect! I really do not know what I did wrong. I just closed down everything and started from scratch and all worked out 100%. This was just a test in Lum on NGC 55 to see what I can get if I spend some time on it. Your prompt assistance are much appreciated and apologies for wasting time on this.
My humble apologies. APP works perfect! I really do not know what I did wrong. I just closed down everything and started from scratch and all worked out 100%. This was just a test in Lum on NGC 55 to see what I can get if I spend some time on it. Your prompt assistance are much appreciated and apologies for wasting time on this.
I am glad that all is allright now. If such a thing happens again, do check the calibrated data with the l-calirbated image viewer mode. That is very usefull to point out a problem with the data or the calibration frames 😉
