Muon HLT updateMuon HLT update

Sergio GrancagnoloSergio Grancagnoloon behalf of the muon slice working groupon behalf of the muon slice working group

Trigger Open MeetingTrigger Open Meeting

Wednesday 18 June 2008Wednesday 18 June 2008

OutlineOutline

• Introduction on Introduction on TrigAlgorithms/TrigMuonEFTrigAlgorithms/TrigMuonEF

• First comparison with First comparison with TrigMooreTrigMoore

• Plans for Plans for TrigMuonEvent/TrigMuonEFInfoTrigMuonEvent/TrigMuonEFInfo

• FDR2FDR2 analysis analysis

• Work done/to doWork done/to do

TrigMuonEFSegmentFinderTrigMuonEFSegmentFinder

TrigMuonEFTrackBuilderTrigMuonEFTrackBuilder

TrigMuonEFExtrapolatorTrigMuonEFExtrapolator

TrigMuonEFCombinerTrigMuonEFCombiner

TrigMuonEFSegmentFinderHypoTrigMuonEFSegmentFinderHypo

TrigMuonEFTrackBuilderHypoTrigMuonEFTrackBuilderHypo

TrigMuonEFExtrapolatorHypoTrigMuonEFExtrapolatorHypo

TrigMuonEFCombinerHypoTrigMuonEFCombinerHypo

MooSegmentCombinationFinderMooSegmentCombinationFinder

MuonCombiTrackMakerMuonCombiTrackMaker

MuidBackTrackerMuidBackTracker

MuidMatchMakerMuidMatchMaker

TrigMuonEF schema in 14.2.0TrigMuonEF schema in 14.2.0

Trigger/TrigAlgorithms/TrigMuonEFTrigger/TrigAlgorithms/TrigMuonEFTrigMuonEF-00-00-22TrigMuonEF-00-00-22

TrigMuonHypo-00-00-71TrigMuonHypo-00-00-71

Starting from TriggerMenuPython-00-01-32Starting from TriggerMenuPython-00-01-32

Dummy hypos for nowDummy hypos for now

InDet EFInDet EF

Containers attached to the TEContainers attached to the TE

TrigMuonEFSegmentFinderTrigMuonEFSegmentFinder

TrigMuonEFTrackBuilderTrigMuonEFTrackBuilder

TrigMuonEFExtrapolatorTrigMuonEFExtrapolator

TrigMuonEFCombinerTrigMuonEFCombiner

MuonSegmentCombinationCollectionMuonSegmentCombinationCollection

TrackCollectionTrackCollection

TrackCollectionTrackCollection forCBforCB

forSAforSA

MuonCombEFMuonCombEFMuidTrackContainerMuidTrackContainer

forTBforTB

forMTforMTMuonPatternCombinationCollectionMuonPatternCombinationCollection

Trk::SegmentCollectionTrk::SegmentCollection

ContainersContainers Retrieve keyRetrieve keySignatureSignaturemu6_efmu6_ef

Uses keys Uses keys forCBforCB,, forSA forSA and and ExtProcTracksExtProcTracks

Starting from TrigMuonEF-00-00-23Starting from TrigMuonEF-00-00-23

Efficiency wrt muComb vs. ptEfficiency wrt muComb vs. pt

Muon Spectrometer only:Muon Spectrometer only: MooreMoore vs.vs. TrackBuilderTrackBuilder

Extrapolation:Extrapolation:MuidSAMuidSA vs.vs. ExtrapolatorExtrapolator

Combination:Combination:MuidCBMuidCB vs.vs. CombinerCombiner

nnEFEF = tracks w/ truth @ DR<0.05 = tracks w/ truth @ DR<0.05

nnL2L2 = tracks w/ truth @ DR<0.1 = tracks w/ truth @ DR<0.1

2L

EF

n

n

Efficiency wrt muComb vs. etaEfficiency wrt muComb vs. eta

Muon Spectrometer only:Muon Spectrometer only: MooreMoore vs.vs. TrackBuilderTrackBuilder

Extrapolation:Extrapolation:MuidSAMuidSA vs.vs. ExtrapolatorExtrapolator

Combination:Combination:MuidCBMuidCB vs.vs. CombinerCombiner

Efficiency wrt muComb vs. phiEfficiency wrt muComb vs. phi

Muon Spectrometer only:Muon Spectrometer only: MooreMoore vs.vs. TrackBuilderTrackBuilder

Extrapolation:Extrapolation:MuidSAMuidSA vs.vs. ExtrapolatorExtrapolator

Combination:Combination:MuidCBMuidCB vs.vs. CombinerCombiner

SA and CB resolution vs. ptSA and CB resolution vs. pt

Extrapolation:Extrapolation:MuidSAMuidSA vs.vs. ExtrapolatorExtrapolator

Combination:Combination:MuidCBMuidCB vs.vs. CombinerCombiner

Current AOD statusCurrent AOD status• TrigMuonEF algorithms write the same AOD object TrigMuonEF algorithms write the same AOD object

of TrigMooreof TrigMooreeasier validationeasier validation– Attached to the TE the TrigMuonEFContainer with Attached to the TE the TrigMuonEFContainer with

different muoncodes:different muoncodes:• TrigMuonEFTrackBuilderTrigMuonEFTrackBuilder 33

• TrigMuonEFExtrapolatorTrigMuonEFExtrapolator 44

• TrigMuonEFCombinerTrigMuonEFCombiner 55

• New AOD object TrigMuonEFInfoContainerNew AOD object TrigMuonEFInfoContainer– Done since Done since TrigMuonEvent-00-00-23TrigMuonEvent-00-00-23

– Persistification seems to work: need to go in cvsPersistification seems to work: need to go in cvs

– Plans to change the shape of this in order to insert Plans to change the shape of this in order to insert TrigMuGirl trackTrigMuGirl track

Muon EF in AOD: minimal proposalMuon EF in AOD: minimal proposal

For each event one For each event one TrigMuonEFInfoContainerTrigMuonEFInfoContainer

For each muon:For each muon:• One istance of One istance of

TrigMuonEFInfoTrigMuonEFInfo• One One TrigMuonEFTrackTrigMuonEFTrack for for

each step of the trigger each step of the trigger TrigMuonEFTrackBuilder TrigMuonEFTrackBuilder TrigMuonEFExtrapolator TrigMuonEFExtrapolator TrigMuonEFCombinerTrigMuonEFCombineror for or for TrigMuGirlTrigMuGirl

• First proposal was using aFirst proposal was using a

P4IPtCotThPhiMP4IPtCotThPhiM

double IPtdouble IPt

double CotThdouble CotTh

double Phidouble Phi

double Massdouble Mass

TrigMuonEFTrack::TrigMuonEFTrack::P4IPtCotThPhiMP4IPtCotThPhiM

bool m_chargebool m_charge

TrigMuonEFInfoTrigMuonEFInfo

unsigned short int m_RoIunsigned short int m_RoI

TrigMuonEFTrack m_spectrometerTrackTrigMuonEFTrack m_spectrometerTrack

TrigMuonEFTrack m_extrapolatedTrackTrigMuonEFTrack m_extrapolatedTrack

TrigMuonEFTrack m_combinedTrackTrigMuonEFTrack m_combinedTrack

TrigMuonEFTrack m_muGirlTrackTrigMuonEFTrack m_muGirlTrack

Get and Set methods to retrieve the right track

std::vector<TrigMuonEFTrack*>std::vector<TrigMuonEFTrack*>

FDR2 Analysis (I)FDR2 Analysis (I)

• First look to muon stream dataFirst look to muon stream data– fdr08_run2.0052290.physics_Muon.merge.AOD.o3_f8_m10._0010.1fdr08_run2.0052290.physics_Muon.merge.AOD.o3_f8_m10._0010.1– "run1" - ideal geometry, 10"run1" - ideal geometry, 103232 cm cm-2-2ss-1-1 average luminosity average luminosity – ~15k events analyzed so far ~15k events analyzed so far

• EF not saved in FDR data (at BS level)EF not saved in FDR data (at BS level)• L1, L2 and TriggerDecision availableL1, L2 and TriggerDecision available

L1 barrel trhesholds wrt off. rec muons (muid)

MU6MU10MU11MU20

muon pT (MeV)

L1 endcap trhesholds wrt off. rec muons (muid)

MU6MU10MU11MU20

muon pT (MeV)

FDR2 Analysis (II)FDR2 Analysis (II)

L2 (muComb) efficiencywrt L1 endcaps

L2 (muComb) efficiencywrt L1 barrel

L2 (muComb) efficiencywrt L1

muon

1 matching offline muon required

no major problems detected,analysis on full sample on going

muon pT (MeV) muon pT (MeV)

MuonStream : Trigger MenuMuonStream : Trigger Menu

L1L2EF

L2/L1

EF/L2

Muon items : L2_mu6 and EF_mu6 not defined in FDR menu

210)(4)(6)

jets

minbias10

20

40

6 + Bphy25i+

10

totalE +

EtMiss

Trigger decision@ EF

ConclusionsConclusionsDone in Done in TrigMuonEF-00-00-25TrigMuonEF-00-00-25 Default RoI size set to 0.2Default RoI size set to 0.2 Corrected filling of AOD objectCorrected filling of AOD object

ppTT in Mev (not in GeV) in Mev (not in GeV) cot(cot() instead of ) instead of RoI indexRoI index

Range of histogramsRange of histograms better comparison with TrigMoorebetter comparison with TrigMoore

RoI size changes for B-sliceRoI size changes for B-slice TrigMoore RoI size overwritten by TrigMoore RoI size overwritten by

Bphysics.pyBphysics.py Switch to TrigMuonEF solve thisSwitch to TrigMuonEF solve this Currently RoI set manually to Currently RoI set manually to

0.2x0.2 for TrigMoore0.2x0.2 for TrigMoore

To do:To do: Understand comparison with TrigMooreUnderstand comparison with TrigMoore Write persistent version of Write persistent version of

TrigMuonEFInfoTrigMuonEFInfo Insert TrigMuGirl track in TrigMuonEFInfoInsert TrigMuGirl track in TrigMuonEFInfo Use of conversion tools for data accessUse of conversion tools for data access Write Write /K rejection hypothesis for new /K rejection hypothesis for new

AOD objectAOD object Correct memory leaks. Leakage whenCorrect memory leaks. Leakage when

objects created by tools are objects created by tools are notnot attached attached to the TE to the TE andand are are notnot deleted by the tools deleted by the tools

Savannah bugs 36483, 37693Savannah bugs 36483, 37693 Cosmic runs require special configuration Cosmic runs require special configuration

for 14.1.0.Xfor 14.1.0.X need help from offline peoplesneed help from offline peoples