1 / 6

Advancements and Future Plans for TrigMoore in HLT Framework

TrigMoore facilitates a seamless interface between online and offline reconstruction in the High-Level Trigger (HLT) framework, specifically under the CVS directory Trigger/TrigAlgorithms/TrigMoore. It operates in two primary modes: Seeded and Wrapped. Current ongoing work includes the debugging of the Muon vertical slice using LVL2 information, combined reconstruction techniques, and evaluations of performance degradation related to background intensity. Future plans involve enhanced track matching, optimization of execution times, and addressing reconstruction challenges posed by pile-up.

aileen-ramirez
Télécharger la présentation

Advancements and Future Plans for TrigMoore in HLT Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TrigMoore: Status, Plans, Possible Milestones

  2. Moore in HLT- status and ongoing work • Package under the CVS directory: Trigger/TrigAlgorithms/TrigMoore • A sort of interface between online and offline reconstruction • It works in the HLT framework • Two main working modes • Seeded • Reconstruction starting from RoI of previous levels. • Wrapped • Full reconstruction, equivalent to the offline working mode • Uses the package MuonIdentification to recontruct (extrapolate) the track back to the interaction point (MuID standalone)

  3. On Going work Moore • Debug of Muon vertical slice • Using the “Muon features” filled by LVL2 • Up to now, the seeded mode has used only LVL1 informations • A first setting of the MuonVerticalSlice, that uses LVL2 informations (muFast) has been implemented and it is under test LVL2 (muFast) LVL1

  4. What’s next? From close next to far next. • Combined Reconstruction • Use of Inner Detector(iPatRec) and MuidCombined in order to match tracks from the Inner Detector and from the Muon Spectrometer and eventually perform a global fit.Ongoing work (foreseen to have a first working version by endof February leader Michela (Napoli) • Reconstruction starting from ByteStream format Ongoing work (foreseen to have a first working version by the second half of February a collaborative work Michela+Gabriella+Ketevi+Stefano • Moore in TestBed (expression of interest from Pavia group: Diana, Max) • Finalized for the Combined testbeam (a possible milestone ? ) • Application of Steering • Analysis for trigger rates using the muons vertical slice LVL1-LVL2-EF with single muons (Lecce, Napoli) • RegionSelector Map extended to Endcaps and to TGC/CSC technologies (Alessandro/Roma1, Gabriella/Lecce) end of February first half of March • A first round on evaluation of executions times and study of possible improvements. Isolation of possible time consuming methods and optimization (Gabriella/Lecce + Moore Offline group) (to start parallely with offline optimization, after 8.0.0 before 9.0.0 DC2)

  5. To do • Evaluation of performance degradation as a function of background intensity and probability of fakes reconstruction (rejection studies) • Preliminary study “OFFLINE” • with pile-up ( 100GeV + bkg) (Margherita/Lecce) - DONE • fakes from K/p (GianPaolo/Napoli) -DONE • Reproduce the studies in TrigMoore (ONLINE) • with pile-up (Margherita/Lecce) – On Going • Fakes studies are dependent on the availability of MuIDCombined • Feedback for offline reconstruction • Use of LVL2 informations from Tile ( At offline level there is work in progress inside the Moore group) (? Some work could start parallely)

  6. Next and hopefully almost ready to start • Second round of optimization of time performance and algorithms • Use of LVL2 infos not used by now. • Access to calibrated data (accessing times and impact on reconstruction performances) • EndCaps extensions (not foreseen a large impact) • Evaluation of Trigger rates for complex (physics events). • Trigger Menu and reconstruction strategy as a function of time/performance • Cosmics rays and commissioning phase

More Related