UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
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
