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.
I like this feature as I like to add filter used and instrument to the FITS headers. But: then the tool creates a .meta second file, and that file is four times the size oif my bin 1 ASI294 FITS file. That is a problem ....
Can the be a way to just batch modify the header data for individual frames without duplicating (and blowing up the size of) the file (like ASTAP can?). That would be super handy!
I will ask Mabula for this, I would've expected it to do that actually.
Dear @heylers,
First of all, what APP version are you using ?
With 2.0.0-beta22 the Batch Modify FITS metadata/CFA tool will also ask you how to save the file with the adjusted FITS header. If you save the data with a higher bit depth, the size will logically be bigger.
If you modify a 32bits mono fits file and tell the save dialog to save it as 32bits float FITS, the size is virtually identical to the original file. Same, if I save a 16bits CFA file to 16bits FITS, also the size is the same except for some bytes. The actual metadata/header is so small it has no bearing here.
To adjust the header directly in the original file is not done by purpose and by request by users in the past. It is always convenient to keep the original file with the original header intact for whatever reason. If the FITS header modification is correct, simply delete the old original fits file if you no longer need it.
Mabula
I'm on beta22. I see it now, on save. My bad!
