Skip to content

Fix unintended PFlow usage in non-PFlow MET

This fixes an issue where MET association maps could be incorrectly constructed using PFOs even if the PFlow option was disabled, if a non-empty FlowElementContainer name is provided. Since 6 July, the MET associators have had a default name for this container, when it became standard to use this instead of the old PFOContainer EDM. This resulted in incorrect MET association maps when built with default settings (e.g. in DAOD_PHYS(VAL)) using 22.0.39 and 22.0.40.

I suspect this issue was responsible for the obviously-incorrect soft term and total MET distributions for EMTopo MET reported in ATLPHYSVAL-797.

Tagging @sawyer, @cdelitzs, @mswiatlo, @bhodkins, for jet/MET and @jferrand, @dhayden for PhysVal.

Merge request reports