Jets scaled by pT instead of energy?

Hi @EdwardMoyse, all,

I recently wrote out some json files for ATLAS events and noticed that jets are defined using eta and phi for angles (as expected) but energy for the magnitude, instead of pT that I would naively have expected. Of course I can fill whatever values I want into the dicts that go into to json, but since the label is "energy" I'm a bit reluctant to fill it with pT (which is quite different at high eta).

Is there a reason why energy is used as label for the magnitude, or could this be replaced with pT? Or maybe left to the user to choose which one to fill, and phoenix would show what's provided (out of a list of valid options like 'pT', 'ET' and 'energy', for example)?

Thanks a lot!

Best,
Christian

Start with guides/users.md, specifically the supported object types section, and trace how the JSON event data is interpreted for jet magnitudes. Decide which magnitude inputs are supported and document or implement the chosen behavior; done means the input convention is unambiguous for ATLAS event JSON users.