Muon Candidate Finders

For every event the following muon candidate finders are called one after the other in the sequence below until a muon is found:

1. Find candidates based on combined muon chamber tracks (see section 6.7.2)
2. Find candidates based on muon chamber tracks (see section 6.7.2)
3. Find candidates based on condensates only (see section 6.7.3)
4. Find halo muon candidates which occur very close to the beam pipe (see section 6.7.4)
5. Find candidates based on the condensate timing (see section 6.7.5)

A very important step to eliminate candidates is based on the following idea: The MUFFIN finder assumes that the reason why an event was taken by the trigger system is the overlapped muon. It assumes that, had the muon not been there, the event would have been rejected.

In the case of the CC sample the traversing muon has increased the of the event and so the event was triggered. This is an important property for a muon candidate and it is used to reduce the sample of possible candidates significantly: Giving a trigger condition such as MUFFIN temporarily removes all candidate cells and tests the condition. If the condition is not fulfilled anymore it means that the candidate might be a traversing muon. Should the condition still be fulfilled it means that the candidate is just a random combination of cells which happened to look like a traversing muon. This check is done at an early stage of the calculation in order to avoid unnecessary calculations.