Skip to content

TrigGlobalEfficiencyCorrectionTool: propagate OutOfvalidityRange code from other tools

When one of the tools providing the per-leg trigger efficiencies returns a CorrectionCode::OutOfvalidityRange, the TrigGlobal tool currently returns a CorrectionCode::Error. The "motivation" was probably the lack of guarantee that this was the only issue affecting the calculation.

However, it was pointed out that this makes the debugging of events with errors quite more difficult, since there are typically no warning printed for OutOfvalidityRange situations. So, this is changed and the tool will now return OutOfvalidityRange for these cases.

cc @jburr

Merge request reports