WCS solution issue #117
Description
The issue was already discussed on slack, but it was decided to open it as a GitHub issue to be fixed properly. I've noticed that quite a few images from my event did not have good WCS solutions. After some discussion, we decided to run the images outside the pipeline with astrometry.net. After the bad solution image was solved with astrometry.net it got a good WCS solution, then I ran the pipeline on that, and then everything was OK. One thing I've noticed is that the bad solution image had a .fits extension while the good ones .fits.fz (fpacked).
Example:
tfn1m001-fa11-20210801-0425-e91.fits (bad WCS solution)
tfn1m001-fa11-20210801-0423-e91.fits.fz (good WCS solution).
(Image files too big to be uploaded)
I note that before going with the astrometry.net solution, I tried all the suggested solutions in the manual.