Apr 9 2026 APP 2.0.0-beta40 has been released !
It has a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration, for mosaics even faster! 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. Improved Outlier Rejection with LN 2.0 rejection. macOS CMD+A works now in file chooser ! And more, all will be added to the release notes in the coming hours...
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.
After integration, APP saves a file of the integrated stack. You can choose to save that yourself also via the 'save' button on the right hand side, but there's no option to save it with a name that you want........ I'm sure that there was a facility to do this in the earlier versions? Am I missing something?
And while I'm thinking about stuff...... would there be a way to disable the automatic save? While I am sure that many will find the huge long file name and auto save very useful and informative..... I prefer to not have an auto save, save what I want and under a name that I like!
Thank you Sara 😉
Currently, there is a very good reason, in my opinion, why APP saves the integration and assigns it with a long file name.
All the integration details, which you want to know for comparison of stacks, aren't yet put in the FITS HEADER.
I will put as much details in the Fits Header of the integration as soon as possible, then the file name can become dynamic and according to your wishes, and you can possibly set this before the integration ?
Can you elaborate why an auto save shouldn't be done? I think I am possibly missing something here 😉 why integrate if you don't save it? Keeping an integration in memory will cause memory problems if the user tries to create a huge mosaic for instance. But then again, maybe I should give you the choice in the 6) Integrate menu?
Cheers,
Mabula
I don't think there's a reason why it shouldn't auto save..... I just personally don't like it. I think that the integrated stack should remain in the cache so that it's there when required and then the user has a choice about whether to auto save or not and how to name it according to their own filing preferences.
Okay Sara, so if I would implement it like this:
After integration, the integration result is directly loaded into the image viewer and you will be presented with the choice, to save it or not, choose a file name yourself by modifying APP's suggestion and also the possibility to save it as TIFF of FITS in bit depths of your choice?
Mabula
Sounds perfect to me!!! From there you can still access it from the lower console area and then you can also use the tools on it as required *thumbs up*
Excellent, will adjust this soon 😉
