You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It does not contain the GH_CUTS HDU information since this HDU is not created by pyirf function. We define the similar function inside the lstchain. Do we need to add the GH_CUTS HDU information in this index table?
The text was updated successfully, but these errors were encountered:
I don't think we use the information from GH_CUTS (or even AL_CUTS) HDU for any high-level analyses. It is mainly used to check the distributions of the cuts applied to get the DL3 file.
Hence it makes less sense to me, to add this information to the HDU index tables (for the sake of completeness).
From #1227
DL3 index table contains the information of IRF HDU.
https://github.com/cta-observatory/cta-lstchain/blob/main/lstchain/high_level/hdu_table.py#L200-L220
It does not contain the GH_CUTS HDU information since this HDU is not created by pyirf function. We define the similar function inside the lstchain. Do we need to add the GH_CUTS HDU information in this index table?
The text was updated successfully, but these errors were encountered: