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.
Something I've noticed lately. Large integrations does not show exposure-time in the FITS header in Pixinsight.
Did an Orion-run yesterday where I did one stack of 20 x 60s exposures (for the core), and another stack of 50 x 300s exposures. Pixinsight does not show the exposure-time for the large integration, but it does show for the small one.
I think this is may be on the APP-side of things, because datasets stacked with older versions of APP does not have this problem.
Â
FITS-header 60s stack from yesterday. Total exposure time is correct (1260) :
FITS-header 300s stack from yesterday. Total exposure time shows an error (1.5E4):
FITS-header from a (large) stack done with an older version of APP a couple of years ago. Correct exposure time (26386):
Â
It could perhaps be something related to 300s exposures, because I also compared to another stack done during the weekend. Less frames than the first one, but there is also an error shown for total exposure time (4.8E3):
FITS-header 300s stack from yesterday. Total exposure time shows an error (1.5E4):
That is not really an error but scientific notation which is usefull when the numbers become big ;-).
1.5E4Â simply means 1.5 * 10^4 = 1.5* 10000 = 15000 seconds.
4.8E3 -> 4.8 * 10^3 = 4,8 * 1000 = 4800 seconds
Mabula
Â
Â
Yes, but why is suddenly 15000, or even 4800 "a too big number" when it previously were able to show over 26k just fine? And why does it only happen with stacks made in newer versions of APP?
It's not that important, but it is a little annoying that I either need to load the stack separately in APP to get a quick view of the total exposure, or keep a separate overview of all the individual light frames, their exposure time and how many of those that were included in the final stack. (or look up a formula)
Hi @wheeljack,
1.5E4is scientific notation and this in fact is an upgrade in the FITS library from NASA that we use, we upgraded that library recently for READ/WRITE FITS support. This notation is just easier and very common in science. If Pixinsight does not understand this? then you should report this there I would think.
"1.5E4 simply means 1.5 * 10^4 = 1.5* 10000 = 15000 seconds."Â
So the exposure time is reported correctly, just in a more compact form.
Mabula
