Open LukasNickel opened 1 year ago
Sorry, I got confused looking at the code. The missing bin edge is added when creating the axes: https://github.com/cta-observatory/cta-lstchain/blob/a8058123c2ab44e7d19dbc44e8de83a1158e562b/lstchain/io/event_selection.py#L450
In that case only the question about the upper edge of 500 TeV remains. Why is it fov_edges, but energy_bins? That is correct, but unexpected
In that case only the question about the upper edge of 500 TeV remains.
50 TeV would be too low, right? CTA requirements are defined up to 200+ TeV - a different issue is how often we will have observations which go beyond a few tens of TeV, but no need to limit that from the start.
50 TeV would be too low, right? CTA requirements are defined up to 200+ TeV - a different issue is how often we will have observations which go beyond a few tens of TeV, but no need to limit that from the start.
How do CTA requirements for the whole array affect the value of the energy migration matrix used for LST mono analysis?
We don't even simulate that high energies
50 TeV would be too low, right? CTA requirements are defined up to 200+ TeV - a different issue is how often we will have observations which go beyond a few tens of TeV, but no need to limit that from the start.
How do CTA requirements for the whole array affect the value of the energy migration matrix used for LST mono analysis?
We don't even simulate that high energies
I may be missing something here... what is the advantage of setting a low value for the E-axis higher end? We may not have data, or MC, until the very end of that range, but does it harm to have a safe limit?
The default energy bins here: https://github.com/cta-observatory/cta-lstchain/blob/main/lstchain/io/event_selection.py#L346
do not match what I would expect:
Is there any deeper meaning behind these values or was there an error in #1036 ?