More informative GTI failure

[matteobachetti]

Responding to an issue by G.L. Israel, I substituted a generic exception with a full traceback of what goes wrong when GTIs are not correctly read.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (cc9d575) 96.31% compared to head (065e3cc) 96.31%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #787   +/-   ##
=======================================
  Coverage   96.31%   96.31%           
=======================================
  Files          43       43           
  Lines        8495     8497    +2     
=======================================
+ Hits         8182     8184    +2     
  Misses        313      313           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pep8speaks]

Hello @matteobachetti! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2024-01-02 17:01:33 UTC

[mgullik]

It definitely makes it more clear what is the error.

Just a thought, could it make sense to set a GTI keyword when reading the fits file?
The default would be the case it is now, but we could give the user the possibility to choose the GTI keyword if they know it for that specific mission.

[matteobachetti]

@mgullik indeed, there is a keyword, gtistring, that allows the user to provide a number of comma-separated strings for GTI extensions. The default is "GTI,STDGTI", or whatever the default for a given mission is