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.
Dear all,
I'd like to suggest to add as much data as possible in the FITS header of the integration and master files, and keep appending to it as the image is processed.
For the integration, the current implementation is already very good, saving all the parameters used in INTEGRATION. But I'd add the data of the Master Calibration files used - this could help solving different versions of calibrations for troubleshooting, for instance. The REGISTER and NORMALIZE settings could also be added in specific tags. I also can look back at the integration and retrace all the steps used to create that file. In the case of saving a stretched image, the header could also incorporate the DDP/stretch parameters.
Finally, and the most important one: when passing an integrated image through any process of 9) TOOL (such as batch modify or LPC), the original header is completely lost. For instance, after using Light Pollution Correction, the saved FITS file has very little information in its header, and all the tags that were in the integration are lost in the subsequent steps.
Best regards,
Gabriel
