Skip to content

Master muon amibiguity processor cleanup

We currently have some serious ambiguity about which ambiguity solver is used. In this MR I attempt to solve this! ;-)

Many tools have a default AmbiSolver type of SimpleAmbiProcessorTool, but since they retrieve the named tool MuonAmbiProcessor (which is of type TrackSelectionProcessorTool), they actually get that. In addition, there is a function called MuonSimpleAmbiProcessorTool, which returns a TrackSelectionProcessorTool(!!!!!).

It's not obvious to me which tool should be being used, but I think step 1) is to clarify the situation.

Additionally, I fixed a few issues with MuonCombinedRecExample caused by !22809 (merged). See ATEAM-530 for details.

Edited by Edward Moyse

Merge request reports

Loading