MOORE (Muon Object Oriented REconstruction) MuonIdentification Track reconstruction in the Muon Spectrometer MuonIdentification Reconstruction and Identification of Muons Divided in two components : MuidStandAlone: Extrapolation of tracks reconstructed by MOORE to the interaction point. 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). When we speak about Moore in the High Level Trigger, we essentially speaks about 3 packages. 1- Moore- is an offline package performing the reconstruction in the Muon Spectrometer. It is able to reconstruct in the full eta range (barrel and endcaps are included). It considers the MuonSpectrometer as a standalone detector (i.e. the tracks reconstructed by Moore are expressed at the first measured point inside the Spectrometer. 2- MuonIdentification- is an offline package dealing with reconstruction and Identification of Muons. It is divided in two components: MuidStandalone - where the tracks reconstructed by Moore are extrapolated to the interaction point taking into account the energy loss and the multiplo scattering in the Calorimeters. MuidComb – where the Moore-tracks are associated with tracks reconstructed in the inner detector (iPatRec), and a combined track is reconstructed Note-MuonIdentification always performs a refit. 3 – TrigMoore – is the implementation of Moore/MuID in the framework of High Level Trigger at the Event Filter stage. Two main strategies have been implemented: Wrapped – Allows to execute the offline reconstruction chain in the online environment (only Moore+MuidStandalone has been implemented.) It allows to reconstruct the event in his completeness accessing all the Spectrometer data. Seeded – uses the Trigger hypothesys from the previous stages (Region Of Interest of the Trigger).

Moore in HLT- a contact point between offline and online. 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. Main ideas Avoid the code duplication! Only the seeding has an ``ad hoc’’ implementation for the online environment. Atlas pcatr machine (2.4GHz) OPT build Timing package: TrigTools/TrigTime Strategies Seeded/wrapped Conservative approach (i.e. data access and data preparation are included) In the table the average and rms is calculated on the events left after rejecting 5% of the events included in the high execution time tail Wrapped, Full event Reconstruction Seeded: Access only the RoI from the LVL1 pT (GeV/c) <T> (msec) rms (msec) 8 73 30 68 20 59 15 58 21 50 61 19 25 100 75 64 26 300 23 32 Here we express the main ideas of the Moore in HLT (in the yellow box it is what has essentially determinated the choice of the 2 strategies. and in the light blue it is a general idea of avoiding duplication. The timing in the table are on the 95 % of the event while the one in the graph include everything and show that very few is spent in the extrapolation to the vertex. The timings are well below the 1 sec requested to process at the EF stage. DC1 single Muons execution times

Wrapped strategy |h| < 1.05 Efficiency for the reconstruction of single Muons sample in wrapped strategy (event scan). This is equivalent to the execution of the offline version of the code. The analysis has been restricted to the barrel region. Resolution in wrapped and seeded strategy. Strategy wrapped |h| < 1.05 Strategy seeded |h| < 1.05 Here we have resolution for seeded and wrapped mode, and efficiency for wrapped mode. In the resolution since there is an ad hoc implementation only for the seeding (search in a limited region and then access to the data) we expect to reproduce the result reported in the offline. The difference on the point at 8GeV/c is related to the trigger threshold used. In this case we have analyzed samples passing the trigger with a configuration threshold of 10 GeV/c therefore we are on a queue.

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. I would show a present work (first part) and how to evolve in the future work. In Particular with Event Filter I want to point out that some real ``analysis’’ on rates and rejection has to be performed including also technical studies as ``Higgs  4 mu’’ how to tag the signal, implementation of the right sequencer after 2 RoIs are found send the ``wrapper’’ and so on.

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 I assume this goes in a general slide, if you need.