Maximilian Linhoff

@adonath I agree there is a large room for improvement here, but as @TarekHC mentioned, there is no one-to-one mapping for observed data, so having a header card in the...

Agree with mostly everything said here. > note that at least for some experiments, these are not spherical coordinates but coordinates in a plane tangential to the array pointing direction...

It's also not mentioned that these columns are lower and upper bin edges respectively. Maybe we should write it like this? ``` Columns: * ``ENERG_LO`` -- ndim: 1, unit: TeV...

Related: also https://github.com/open-gamma-ray-astro/gamma-astro-data-formats/issues/102 for defining a solution to define the axis order properly in the header. But +1 for having the *recommended* axis order consistent

@adonath I disagree, I think the actual IRF axes should always be the last. so `[general binning dims, irf dims]`. That allows to be consistent over all the irfs.

> Separating ENERG from MIGRA would not allow displaying the energy migration matrix using fv for example. I don't understand this statement. What does the order of the axes have...

@adonath Yes, I think having the energy closest to the irf dims makes sense for many use cases, maybe this is also what @jknodlseder was referring to?

And it doesn't allow choosing which Axes of a row in a binary table should be displayed? If yes, do we really need to support this use case, if we...

But it has no support for the GADF data formats other than that we use FITS files, and I guess the EDISP matrix is the only IRF that displays nicely....

So I thought I was missing out maybe and installed fv. I used the DL3 files from the HESS Data Release 1 used for the open crab paper and pressed...