Maximilian Linhoff
Maximilian Linhoff
This, by the way, goes also back to #102, as in we shouldn't really prescribe an axis order (or maybe we should) but require using a consistent method the description...
On a side note, I think we should call them not by their shape but find more appropriate names. E.g. 2d could be `AEFF_RAD` for radially symmetric, 3D could be...
Just to add: we probably then can use the same format also for background and psf tables that are not radially symmetric in the FOV
> DETX and DETY are in reconstructed coordinates, while effective area should be a function of true incident angle. Are you proposing to have a coordinate system for true coordinates...
Also the required columns would need to be different, as most simulations won't have well-defined RA / DEC / TIME
@cosimoNigro We would also need a table for energy dependent cuts.
@cosimoNigro We already have a RAD_MAX table for energy / fov dependent cuts. I don't see a reason why we should restrict us to a global gammaness cut, we know...
Yes, indeed. You do not to know gammaness cuts for the analysis of already selected events for DL3 data. However, for provenance it might be good to define it in...
> If we add that column, we would need IRFs also evolving in bins of gammaness (including of course the background model). I think this is not true. Just adding...
The same as for the other definitions, to have a common data format for easy exchange and processing of such data. Right now, one of the use cases would be...