1 / 18

Muon HLT: status of the algorithms and performance

Muon HLT: status of the algorithms and performance. Sergio Grancagnolo for the Muon HLT group. Summary. Performances Efficiencies of muFast, muComb, TrigMoore Efficiencies and p T resolutions for MuidSA and MuidCB EF Comparison TrigMuonEF vs TrigMoore

eliza
Download Presentation

Muon HLT: status of the algorithms and performance

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: status of the algorithms and performance Sergio Grancagnolo for the Muon HLT group

  2. Summary • Performances • Efficiencies of muFast, muComb, TrigMoore • Efficiencies and pT resolutions for MuidSA and MuidCB • EF • Comparison TrigMuonEF vs TrigMoore • TRT only chains: comparison with all ID reconstruction

  3. LVL2: muFast efficiency wrt LVL1 vs. pT vs. eta e322_s461_r534 OFLCOND-SIM-00-00-03 e322_s461_r535known problems of the real detector (dead channels, noisy channels, etc.)

  4. LVL2: muComb efficiency wrt LVL1 vs. pT vs. eta e322_s461_r534 e322_s461_r535

  5. EF: MS reconstruction wrt LVL2 vs. pT vs. eta e322_s461_r534 e322_s461_r535

  6. EF: Muon extrapolated and combined reconstruction wrt LVL2 Combination Extrapolation e322_s461_r534 e322_s461_r535

  7. Muon EF: pT resolution Combination Extrapolation e322_s461_r534 e322_s461_r535

  8. TrigMuonEF - Introduction • Validation of TrigMuonEF wrt TrigMoore performance • Based on AODs produced in 14.2.20, bugfix + tags to fix bug #39808 • MuonRdoToPrepData-01-03-14 • RecExCond-00-01-39 • MuonRecExample-00-13-20 • Only mu6 (TrigMoore) and mu6_ef (TrigMuonEF) enabled • Consistent threshold cuts at L2 • valid3.005200.T1_McAtNlo_Jimmy.digit.RDO.e322_s46 • ~19k ttbar events 8

  9. Efficiency vs eta TrigMoore Efficiency w.r.t. L2 muComb TrigMuonEF Efficiency Efficiency Extrapolator (MuidStandalone) MS extrapolated @IP Combined (MuidCombined) h h 9

  10. Turn-on curves Efficiency Efficiency Full circles = TrigMoore Open circles = TrigMuonEF Extrapolator barrel Extrapolator endcaps Efficiency w.r.t. L2 muComb pt pt No cuts Efficiency Efficiency pT > 6 GeV Combined barrel Combined endcaps pT > 20 GeV pT > 40 GeV pt pt 10

  11. Fake and good tracks Same DR (<0.1) cut for both extrapolation and combined • ttbar • events TrigMoore TrigMuonEF TrigMoore TrigMoore TrigMuonEF TrigMuonEF DR distribution extrapolator DR distribution combined 11

  12. eta-phi resolutions vs pt • Each resolution (eta,phi) at vertex is comparable • The TrigMuonEFExtrapolator has worse phi resolution than TrigMoore TrigMuonEF extrapolator TrigMuonEF combined TrigMoore extrapolator TrigMoore combined 12

  13. pT Resolutions • The TrigMuonEFExtrapolator has sligthly better pT resolution than TrigMoore for pT<40GeV TrigMoore TrigMuonEF PT resolution PT resolution Extrapolator (MuidStandalone) Combined (MuidCombined) pt pt 13

  14. LVL2 ID tracking with TRT Using TRTSegFinder_Muon on a cosmic run No tracks combined Need to pass to the cosmic configuration for ID algos • muComb code with TRT only ready (TrigmuComb-00-00-42) • Not yet in the release • Require a LVL2 chain under developement

  15. Setup to run TrigMuonEF with TRT only • Tested on val,rel_2,14.2.30 (last week) with testMuonSliceAthenaModernRDO.py on tt events • Tags required • Reconstruction/MuonIdentification/MuidCombinedTools-00-03-01 • Trigger/TrigAlgorithms/TrigMuonEF-00-00-48 • Instead of • TrigEFIDInsideOut_Muon() • TrigMuonEFCombinerConfig() use • TrigEFIDOutsideInTRTOnly_Muon() • TrigMuonEFCombinerConfigTRTOnly() within Trigger/TriggerCommon/TriggerMenuPython/python/Muon.py • TrigMuonEFCombiner configured with • MuidMatchMaker.MatchTrtTracks = True • self.IdTracks = "InDetTrigTrackSlimmerTRTOnly_Muon_EFID" • ID tracks name changed from InDetTrigParticleCreation_Muon_EFID to InDetTrigParticleCreationTRTOnly_Muon_EFID

  16. Comparison TRT only / all ID • Number of TRT hits shown • More TRT only tracks reconstructed Entries 4143 Entries 4365 TRT only All ID Tracks that do not reack TRT

  17. Comparison TRT only / all ID (II) • eta distribution for MS-ID combined tracks • Fake TRT only tracks killed in combination • Lost tracks are outside the TRT acceptance Entries 884 Entries 811 TRT only All ID

  18. Conclusions • Muon HLT is performing well • Transition to TrigMuonEF ready • To be enabled the pT hypo algo if requested • First results with TRT only tracks encouraging • To complete configuration for LVL2

More Related