1 / 14

Muon HLT update

Muon HLT update. Sergio Grancagnolo on behalf of the muon slice working group Trigger Open Meeting Wednesday 18 June 2008. Outline. Introduction on TrigAlgorithms/TrigMuonEF First comparison with TrigMoore Plans for TrigMuonEvent/TrigMuonEFInfo FDR2 analysis Work done/to do.

ivory
Download Presentation

Muon HLT update

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. Muon HLT update Sergio Grancagnolo on behalf of the muon slice working group Trigger Open Meeting Wednesday 18 June 2008

  2. Outline • Introduction on TrigAlgorithms/TrigMuonEF • First comparison with TrigMoore • Plans for TrigMuonEvent/TrigMuonEFInfo • FDR2 analysis • Work done/to do

  3. TrigMuonEF schema in 14.2.0 InDet EF Trigger/TrigAlgorithms/TrigMuonEF TrigMuonEF-00-00-22 TrigMuonHypo-00-00-71 Dummy hypos for now TrigMuonEFSegmentFinder MooSegmentCombinationFinder TrigMuonEFSegmentFinderHypo TrigMuonEFTrackBuilder MuonCombiTrackMaker TrigMuonEFTrackBuilderHypo TrigMuonEFExtrapolator MuidBackTracker TrigMuonEFExtrapolatorHypo TrigMuonEFCombiner MuidMatchMaker TrigMuonEFCombinerHypo Starting from TriggerMenuPython-00-01-32

  4. Containers attached to the TE Signature mu6_ef Retrieve key Containers TrigMuonEFSegmentFinder MuonSegmentCombinationCollection forTB MuonPatternCombinationCollection Trk::SegmentCollection forMT TrigMuonEFTrackBuilder forSA TrackCollection TrigMuonEFExtrapolator forCB TrackCollection Uses keys forCB, forSA and ExtProcTracks TrigMuonEFCombiner MuidTrackContainer MuonCombEF Starting from TrigMuonEF-00-00-23

  5. Efficiency wrt muComb vs. pt Muon Spectrometer only: Moorevs.TrackBuilder Extrapolation: MuidSAvs.Extrapolator Combination: MuidCBvs.Combiner nEF = tracks w/ truth @ DR<0.05 nL2 = tracks w/ truth @ DR<0.1

  6. Efficiency wrt muComb vs. eta Muon Spectrometer only: Moorevs.TrackBuilder Extrapolation: MuidSAvs.Extrapolator Combination: MuidCBvs.Combiner

  7. Efficiency wrt muComb vs. phi Muon Spectrometer only: Moorevs.TrackBuilder Extrapolation: MuidSAvs.Extrapolator Combination: MuidCBvs.Combiner

  8. SA and CB resolution vs. pt Extrapolation: MuidSAvs.Extrapolator Combination: MuidCBvs.Combiner

  9. Current AOD status • TrigMuonEF algorithms write the same AOD object of TrigMooreeasier validation • Attached to the TE the TrigMuonEFContainer with different muoncodes: • TrigMuonEFTrackBuilder 3 • TrigMuonEFExtrapolator 4 • TrigMuonEFCombiner 5 • New AOD object TrigMuonEFInfoContainer • Done since TrigMuonEvent-00-00-23 • Persistification seems to work: need to go in cvs • Plans to change the shape of this in order to insert TrigMuGirl track

  10. Muon EF in AOD: minimal proposal For each event one TrigMuonEFInfoContainer For each muon: • One istance of TrigMuonEFInfo • One TrigMuonEFTrack for each step of the trigger TrigMuonEFTrackBuilder TrigMuonEFExtrapolator TrigMuonEFCombiner or for TrigMuGirl • First proposal was using a std::vector<TrigMuonEFTrack*> Get and Set methods to retrieve the right track

  11. MU6 MU6 MU10 MU10 MU11 MU11 MU20 MU20 L1 barrel trhesholds wrt off. rec muons (muid) L1 endcap trhesholds wrt off. rec muons (muid) muon pT (MeV) muon pT (MeV) FDR2 Analysis (I) • First look to muon stream data • fdr08_run2.0052290.physics_Muon.merge.AOD.o3_f8_m10._0010.1 • "run1" - ideal geometry, 1032 cm-2s-1 average luminosity • ~15k events analyzed so far • EF not saved in FDR data (at BS level) • L1, L2 and TriggerDecision available

  12. FDR2 Analysis (II) 1 matching offline muon required no major problems detected, analysis on full sample on going L2 (muComb) efficiency wrt L1 muon h L2 (muComb) efficiency wrt L1 barrel L2 (muComb) efficiency wrt L1 endcaps muon pT (MeV) muon pT (MeV)

  13. L2/L1 L1 EF/L2 L2 EF MuonStream : Trigger Menu minbias Trigger decision @ EF m10 jets m20 totalE + EtMiss m6 + Bphy 2m(10)(4)(6) t25i + m10 m40 Muon items : L2_mu6 and EF_mu6 not defined in FDR menu

  14. Done in TrigMuonEF-00-00-25 Default RoI size set to 0.2 Corrected filling of AOD object pT in Mev (not in GeV) cot(q) instead of q RoI index Range of histograms better comparison with TrigMoore RoI size changes for B-slice TrigMoore RoI size overwritten by Bphysics.py Switch to TrigMuonEF solve this Currently RoI set manually to 0.2x0.2 for TrigMoore To do: Understand comparison with TrigMoore Write persistent version of TrigMuonEFInfo Insert TrigMuGirl track in TrigMuonEFInfo Use of conversion tools for data access Write p/K rejection hypothesis for new AOD object Correct memory leaks. Leakage when objects created by tools are notattached to the TE and arenot deleted by the tools Savannah bugs 36483, 37693 Cosmic runs require special configuration for 14.1.0.X need help from offline peoples Conclusions

More Related