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.
Immediately after completing integration, I did a save of the result. I chose to save in FITS format. I expected doing that would produce an exact copy of the FITS file that was automatically saved by APP after the integration process completes. I was surprised to find that the automatically saved file had a size of 365 MB, while the file I saved manually had a size of 91.2 MB.
Â
Why do these two FITS files differ so much in size? What information is present in the automatically saved file that is missing from the manually saved file?
Hi,
I'm not sure of this but I suggest you take a look at the FITS header info for the relevant files.
There is a header field NAXIS.
On the smaller file I suspect the NAXIS value will be 2, corresponding to a single channel (i.e. mono) image file with height and width dimensions.
On the larger file I suspect the NAXIS value will be e.g. 3, corresponding to a three channel (i.e. tri-color RGB) image file.
The AXIS values are given by NAXIS1, NAXIS2...NAXISn etc. corresponding to the number of data dimension. NAXIS1 & 2 will have values corresponding to the height and width of your image. NAXIS3 will have a value corresponding to the number of channels provided for in the image file, i.e 3 for an RGB image.
I suspect that following integration APP knows it is saving a single channel file but subsequently when the right hand SAVE button is pressed it assumes the file to be save is 3 channel, eg the saved file has provision for three channels as would exist once the Combine RGB process had been completed.
The FITS header info in the manual-saved image file has fewer fields compared with the auto saved file but the large size increase is due to provision for two extra image channels that presumably contain only null values.
Looking at my files I see the manually saved files are almost exactly 3x the mono files. In your case the size is 4x so maybe the NAXIS3 value on your larger file is 4 rather than 3, maybe Luminance.
Hope this helps answer your question
Mike
Â
