That should not happen. I tested it here and I can not reproduce the effect.
I vaguely remember this happened briefly a few weeks ago and was almost immediately fixed. Version 2026-10-14 should not have it. I tested the Linux version. Can you download a fresh copy of ASTAP and try again?
If the effect is persistent, can you create a small test set of frames to reproduce the effect? Then share it and I can test it here.
The -4712-01-01T12:00:00 is a separate issue. This is the year 0 of the Julian day calculation. Weird, looks like the date was not readable. Do you use DSLR images? Send a sample to reproduce the problems.
cs, Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have found the cause. The reason there is no dark is available, only the flat.. This is rare. Normally you would at least apply the dark. Some people skip the flat. You did the opposite.
The fix is one line extra code. It will be fixed in the next version.
cs, Han
❤️
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems that when stacking, the
CALSTATfield in the header of the output FITS file gets oneFletter for every subframe that was flat-calibrated.For example:
(
fitstoolabove is my toy program that dumps the FITS header of a file)Is this intended? I wasn't able to find a specification of this field, but I admit not looking deep...
With a lot of subframes, this leads to apprarently invalid header. At least the
astrogo/fitsiolibrary complains about it: https://codeberg.org/astrogo/fitsio/issues/61First noticed in an old version of ASTAP, but just reproduced with version 2026-10-14.
regards,
Marcin
Turns out the
fitsiodeveloper also noticed another corrupted field:I wonder if this is a result of the overflow, or a separate issue.
Hi Marcin,
That should not happen. I tested it here and I can not reproduce the effect.
I vaguely remember this happened briefly a few weeks ago and was almost immediately fixed. Version 2026-10-14 should not have it. I tested the Linux version. Can you download a fresh copy of ASTAP and try again?
If the effect is persistent, can you create a small test set of frames to reproduce the effect? Then share it and I can test it here.
The -4712-01-01T12:00:00 is a separate issue. This is the year 0 of the Julian day calculation. Weird, looks like the date was not readable. Do you use DSLR images? Send a sample to reproduce the problems.
cs, Han
Interesting. Here is a zip with the inputs and outputs, and here is the procedure I used:
Thanks. I can reproduce the problem here. Now I have to find out why this happens.....
I have found the cause. The reason there is no dark is available, only the flat.. This is rare. Normally you would at least apply the dark. Some people skip the flat. You did the opposite.
The fix is one line extra code. It will be fixed in the next version.
cs, Han