MOORE MOORE (Muon Object Oriented REconstruction) Track reconstruction in the Muon Spectrometer

MuonIdentificationMuonIdentification Reconstruction and Identification of Muons Divided in two components :

MuidStandAlone:MuidStandAlone: Extrapolation of tracks reconstructed by MOORE to the interaction point.

MuidComb:MuidComb: Combination of tracks reconstructed inside the Muon Spectrometer with tracks reconstructed in the Inner Detector

TrigMoore: Implementation of MOORE/MuID in the framework of High Level Trigger at the Event Filter stage. Wrapped Strategy- Allows to execute the offline reconstruction chain from the online

environment, reconstructing the event by accessing at all the Spectrometer data. The implemented chain is composed by Moore and MuidStandAlone.

Seeded Strategy – Uses the hypotesys formed at the previous stage in the trigger process, accessing only to subdetectors data that are of interest for the selected trigger regions. (By now only regions selected by the LVL1 trigger have been used).

Moore in HLT- a contact point between offline and online.

Main ideas

The algorithms operating in the High Level Trigger at the Event Filter stage should not operate only in a general purpose mode (reconstructing the event in full scan) but should be able to operate starting from hypothesys formed in the previous stages of the triggering process.

Avoid the code duplication! Only the seeding has an ``ad hoc’’ implementation for the online environment.

RecMuonRoI

( ±±)RegionSelector Hash offline IDs

DigitsCollection

(RPCs and MDTs)

RPCDigitContainerMDTDigitContainer

TDS(ZEBRA)

MooMakePhiSegmentSeededMooMakeRZSegmentSeeded

PhiSegmentContainerRZSegmentContainer

(TDS)

MooMakeRoadsMooMakeTracksTracks

MooHLTAlgodecision

TrigMoore timing tests (I) Atlas pcatr machine (2.4GHz) Atlas pcatr machine (2.4GHz) OPT buildOPT build Timing package: TrigTools/TrigTimeTiming package: TrigTools/TrigTime Strategies Seeded/wrappedStrategies Seeded/wrapped Conservative approach (i.e. data access

and data preparation are included)

Timing test performed on 6.0.4 release Timing test performed on 6.0.4 release Timing test performed on 6.0.4 release Timing test performed on 6.0.4 release

DC1 single Muons DC1 single Muons execution timesexecution timesDC1 single Muons DC1 single Muons execution timesexecution times

TailsTailsTailsTails

TrigMoore timing tests(II)

DC1 single Muons DC1 single Muons execution timesexecution timesDC1 single Muons DC1 single Muons execution timesexecution times

Timing test performed on 6.0.4 release Timing test performed on 6.0.4 release Timing test performed on 6.0.4 release Timing test performed on 6.0.4 release

In the table the average and rms is In the table the average and rms is calculated on the events left after rejecting calculated on the events left after rejecting 5% of the events included in the high 5% of the events included in the high execution time tail execution time tail

Wrapped, Full event Reconstruction

Seeded: Access only the RoI from the LVL1

pT

(GeV/c)<T> (msec)

rms (msec)

<T> (msec)

rms (msec)

8 73 30 68 30

20 59 15 58 21

50 61 19 58 25

100 61 75 64 26

300 75 23 64 32100+X1 763 37 2680 450100+X2 1218 50 5900 1100

Single Muons + Pile upSingle Muons + Pile upSingle Muons + Pile upSingle Muons + Pile up

TrigMoore timing efficiency

A time efficiency has been defined as the ratio between the number of reconstructed tracks in one second and the total number of reconstructed tracks

A time efficiency has been defined as the ratio between the number of reconstructed tracks in one second and the total number of reconstructed tracks

DC1 single MuonsDC1 single MuonsDC1 single MuonsDC1 single Muons

Wrapped strategy || < 1.05Wrapped strategy || < 1.05

Efficiency for the reconstruction of single Muons Efficiency for the reconstruction of single Muons sample in sample in wrappedwrapped strategy ( strategy (event scanevent scan). This is ). This is equivalent to the execution of the offline version of the equivalent to the execution of the offline version of the code. The analysis has been restricted to the barrel code. The analysis has been restricted to the barrel region.region.Resolution in Resolution in wrappedwrapped and and seeded seeded strategy.strategy.

Strategy seeded || < 1.05Strategy seeded || < 1.05Strategy wrapped || < 1.05Strategy wrapped || < 1.05

Present and Future work.

MOORE in release 6.6.0 towards 7.0.0 Migration to gcc3.2 accomplished Wrapped strategy (working)

Seeded strategy (no RecoRoI from LVL1)

After release 6.6.0 more general changes have to be considered (e.g. Compact Identifiers- Id Helpers). Those changes effect the MOORE execution time. Timing table has to be evaluated once again

Implementation of the complete Muon slice Read LVL2 output results (see G.Comune presentation)

Efficiency curves and trigger rates Calculation of efficiency curves and trigger rates using single muons sample Calculation of efficiency curves and trigger rates using realistic event samples

EventFilter Selection on Physic samples

RPC bytestream converters Full online implementation of TrigMoore.

List of related papers

ATLAS notes for more information: Moore as Event Filter in the ATLAS High Level Trigger ATL-SOFT-2003-008, ATL-DAQ-2003-020

Track reconstruction in the ATLAS Muon Spectrometer with MOORE ATL-SOFT-2003-007