Skip to content

ATR-27067: Initial implementation of Tight eEM eta-dependent cuts

Teng Jian Khoo requested to merge khoo/athena:23.0-TMMT-eFEXTightEtaDep into 23.0

Attn @hillier, @thompson

This is a first go at putting the eta-dependent cuts in the menu as requested on ATR-27067. Does this look right to you?

I assumed that the 50 values are meant to be eta-symmetric values, which appear in the menu as follows (only the terminal values extracted):

{
    "reta_fw": 86,
    "reta": 0.085,
    "wstot_fw": 0,
    "wstot": 0,
    "rhad_fw": 250,
    "rhad": 0.031,
    "etamin": 49,
    "etamax": 50,
    "priority": 2
},
{
    "reta_fw": 86,
    "reta": 0.085,
    "wstot_fw": 0,
    "wstot": 0,
    "rhad_fw": 250,
    "rhad": 0.031,
    "etamin": -50,
    "etamax": -49,
    "priority": 2
}

I note that the previous values only run to eta bins at +/-49. Should the priority 0 ranges be extended?

Another point to be verified -- I understood that we should still keep wstot cuts at 0 explicitly despite the provided values -- please let me know if I have misunderstood.

The new dictionary containing the cut values only needs to contain any eta-dependent cuts that are wanted, so working points that are intended not to have these ranges will just ignore it. I don't think it is necessary to allow the priority to be specified in any greater detail (i.e. allow for different ranges with different priorities in the new file). That said, at present the ranges specified will supersede everything else that has been entered with priority 0,1, so this could be revisited.

The eta range and granularity are explicit in the dict, so that there is the possibility to do this in a more limited range only. Only one, however, we can't do disjoint ranges.

FYI @astruebi, @lidiaz

Edited by Teng Jian Khoo

Merge request reports