Muon Reconstruction/Trigger Performance with TGC 1 Bunch Readout Mode
Koji Sato
MTSG meeting
July 21, 2014
1
Motivation• TGC ROD busy caused a lot of downtime in 2012.• Significant amount (0.35 fb-1) of collisions were lost due to
this problem.
↓• Track down the source of the problem (→electrical
disturbance).• Implement a scheme to reject events with burst of noise to
the trigger system.• Minimize data size, and allow more events in the readout
buffer.– TGC read outs hits from 3 bunches:
• Previous, current and next bunch– Does the muon quality degradate, if we only read out the
current bunch? (1 bunch readout)
2
I show a study of offline muon properties this time.How the change affects the trigger is under study.
3
RunNumber 215473 EventNumber 39074754
Burst Event ②CAL
TGC + CAL
RPC + TGC + CAL
MDT + RPC + TGC + CAL
From Masato’s slides: TDAQ Week, 8 July 2013
Analyzed DatasetsDataset name # events Simulated for 1
bunch readout
data data12_8TeV.00215433.physics_Muons.merge.RAW
5,869,910 Offline reco
MC mc12_8TeV.147807.PowhegPythia8_AU2CT10_Zmumu.recon.RDO.e1852_a220_a225_tid01403231_00
249,500 Trigger simOffline reco
MC mc12_8TeV.208002.Pythia8B_AU2_CTEQ6L1_pp_Jpsimu6mu6.recon.RDO.e1331_a159_a190
499,000 Trigger simOffline reco
4
Run 215433: Nov 30, 2012 Peak lum=6.7e33 Int Lum=123 pb-1
Today, I will show plots showing all the combined muons (EF/L2 and Offline) found in the D3PDs.
EF muon distributions• Plotting distributions of EF muons with mu6 bit and
associated with CB tracks. Blue: 3 bunch readoutRed: 1 bunch readout
𝑁 (𝐸𝐹𝑚𝑢𝑜𝑛𝑠)
𝑚𝑢𝑜𝑛𝑃𝑡
𝑍→𝜇𝜇𝑀𝐶 𝐽 /𝜓→𝜇𝜇𝑀𝐶
6
EF muon distributions• Plotting distributions of EF muons with mu6 bit and
associated with CB tracks.
𝑚𝑢𝑜𝑛𝜙
𝑍→𝜇𝜇𝑀𝐶 𝐽 /𝜓→𝜇𝜇𝑀𝐶
𝑚𝑢𝑜𝑛𝜂
7
Blue: 3 bunch readoutRed: 1 bunch readout
Difference in Simulated EF Trigger Muons, Z->mumu MC
• Plotting (1bunch – 3bunch mode)
EF muons with mu6 bit
Δ𝜂𝜇 Δ𝜙𝜇❑
Δ 𝑅𝜇 Δ 𝑃𝑡𝜇
Similar results from J/psi sample• No difference in # EF muons• Very slight change in kinematics for few events 8
L2 muon distributions• Plotting distributions of L2 comb muons with mu6 bit.
𝑁 (𝐸𝐹𝑚𝑢𝑜𝑛𝑠)
𝑚𝑢𝑜𝑛𝑃𝑡
𝑍→𝜇𝜇𝑀𝐶 𝐽 /𝜓→𝜇𝜇𝑀𝐶
9
Blue: 3 bunch readoutRed: 1 bunch readout
Difference in Simulated L2 Trigger Muons, Z->mumu MC
• Plotting (1bunch – 3bunch mode)
muons with mu6 bit
Δ𝜂𝜇 Δ𝜙𝜇❑
Δ 𝑅𝜇 Δ 𝑃𝑡𝜇
Similar results from J/psi sample• No difference in # L2 muons• No change in kinematics 11
L1 muon distributions• Plotting L1 muons without requiring trigger bit.• D3PD only contains L1 bit for event.
𝑁 (𝐸𝐹𝑚𝑢𝑜𝑛𝑠)
𝑚𝑢𝑜𝑛𝑃𝑡
𝑍→𝜇𝜇𝑀𝐶 𝐽 /𝜓→𝜇𝜇𝑀𝐶
12
Blue: 3 bunch readoutRed: 1 bunch readout
Difference in Simulated L1 Trigger Muons, Z->mumu MC
• Plotting (1bunch – 3bunch mode)
Δ𝜂𝜇 Δ𝜙𝜇❑
Δ 𝑅𝜇 Δ 𝑃𝑡𝜇
Similar results from J/psi sample• No difference in kinematics
• We expect no difference for L1, since L1 muon trigger only considers Current bunch hits.
14
Summary of Trigger Muon Properties• I compared simulated trigger muons between 1 and 3
bunch readout scheme for TGC.– Using and MC samples.– Only slight difference in kinematic properties of EF
muons were seen for a few events in sample.
15
COMPARISON OF OFFLINE RECONSTRUCTIONPrevious presentation at MTSG on Jan 27, 2014, where reconstructed muons were looked at in data:
https://indico.cern.ch/event/296921/
Updates are:• Muon eta regioning is updated.• Also looking at MC samples.
16
Offline Reconstructed Muons (Full Stat.)• CB muons of MUONS collection, Pt>7 GeV
17
Blue: 3 bunch readoutRed: 1 bunch readout
Offline Reconstructed Muons (small stat.)
• CB muons of MUONS collection in 1.1<|η|<1.6. MC MC 𝐷𝑎𝑡𝑎
𝑚𝑢𝑜𝑛𝑃𝑡
𝑚𝑢𝑜𝑛𝜂
𝑚𝑢𝑜𝑛𝜙
18
Blue: 3 bunch readoutRed: 1 bunch readout
Offline Reconstructed Muons (small stat.)
• CB muons of MUONS collection in 1.1<|η|<1.6. MC MC 𝐷𝑎𝑡𝑎
𝑚𝑢𝑜𝑛𝑃𝑡
𝑚𝑢𝑜𝑛𝜂
𝑚𝑢𝑜𝑛𝜙
19
Blue: 3 bunch readoutRed: 1 bunch readout
Offline Reconstructed Muons (small stat.)
• CB muons of MUONS collection in 1.1<|η|<1.6. MC MC 𝐷𝑎𝑡𝑎
𝑛𝑇𝐺𝐶𝐸𝑡𝑎𝐻𝑖𝑡𝑠
h𝑛𝑇𝐺𝐶𝑃 𝑖𝐻𝑖𝑡𝑠
MC MC 𝐷𝑎𝑡𝑎
20
Blue: 3 bunch readoutRed: 1 bunch readout
Offline Reconstructed Muons (small stat.)
• CB muons of MUONS collection in 1.1<|η|<1.6. MC MC 𝐷𝑎𝑡𝑎
𝑛𝑇𝐺𝐶𝐸𝑡𝑎𝐻𝑖𝑡𝑠
h𝑛𝑇𝐺𝐶𝑃 𝑖𝐻𝑖𝑡𝑠
21
Blue: 3 bunch readoutRed: 1 bunch readout
Difference in Offl. Reco Variables, Z->mumu MC
• Plotting (1bunch – 3bunch mode)Δ𝑁𝜇 ,𝑃𝑡 (𝜇>7GeV )
Δ𝑁𝜇 ,𝑛𝑜𝑃𝑡 𝑐𝑢𝑡 Δ𝜂𝜇 Δ𝜙𝜇❑
Δ 𝑅𝜇 Δ 𝑃𝑡𝜇
23
Difference in Offl. Reco Variables, J/psi->mumu MC
• Plotting (1bunch – 3bunch mode)Δ𝑁𝜇 ,𝑃𝑡 (𝜇>7GeV )
Δ𝑁𝜇 ,𝑛𝑜𝑃𝑡 𝑐𝑢𝑡 Δ𝜂𝜇 Δ𝜙𝜇❑
Δ 𝑅𝜇 Δ 𝑃𝑡𝜇
24
Difference in Offl. Reco Variables, Data
• Plotting (1bunch – 3bunch mode)Δ𝑁𝜇 ,𝑃𝑡 (𝜇>7GeV )
Δ𝑁𝜇 ,𝑛𝑜𝑃𝑡 𝑐𝑢𝑡 Δ𝜂𝜇 Δ𝜙𝜇❑
Δ 𝑅𝜇 Δ 𝑃𝑡𝜇
25
Muons of 3 BC scheme matched to 1 BC muon within dR<0.01
Pt
eta phi author
nTGCEtaHitsnTGCPhiHits
Data
26
Muons of 3 BC scheme matched to 1 BC muon within 0.01<dR<0.1
Pt
eta phi author
nTGCEtaHitsnTGCPhiHits
Data
27
Muons of 3 BC scheme having no matched 1 BC muon within dR <0.1
Pt
eta phi author
nTGCEtaHitsnTGCPhiHits
Data
28
Summary of Offline Muon Properties• Compared properties of offline reconstructed CB MUONS
with Pt>7 GeV.– Using and MC samples.
• Only found one muon reconstructed with ~0.001 change in eta and phi.
– Using Muons.Merge Data of Run 215433. • 99.86% of muons of 3 BC scheme find a matched 1
BC muon within dR<0.01.– 3,139,971 (3,139,888) muons were found with 3 (1) bunch
scheme, in 3512939 events.– 3,135,629 muons of 3 BC scheme have a matched muon of 1
BC scheme within dR<0.01.– 1,281 muons have a matched 1BC muon within 0.01<dR<0.1.– 3,061 muons don’t have a matched 1 BC muon within dR<0.1.
29
Summary• Almost no difference is seen between 1 and 3 bunch
readout schemes in terms of CB muon quantities of trigger and offline muons in MC studies.
• ~0.1% of 3 BC muons in data don’t get reconstructed in 1 BC scheme.
• The results of offline studies of data and MC don’t look very consistent.
• Is there anything MC samples doesn’t correctly simulate? Is its simulation of prev. and next bunch collisions tuned well?
• Implementation of 1 bunch readout to Athena code is different between data and MC.
• Plan to reprocess data but with MC Athena code, and see if the results change.
30
Motivation• TGC ROD busy caused a lot of downtime in 2012.• Significant amount (0.35 fb-1) of collisions were lost due to
this problem.
Summary of 2012 Downtime:Total: 1.6 fb-1
Start/end of run: 0.6 fb-1 Deadtime: 1.0 fb-1
Luminosity in 2012:Delivered: 23.3 fb-1
Atlas Recoded: 21.7 fb-1
32
33
RunNumber 215473 EventNumber 39074754
Burst Event ②CAL
TGC + CAL
RPC + TGC + CAL
MDT + RPC + TGC + CAL
From Masato’s slides: TDAQ Week, 8 July 2013
TGC problem in 2012
• TGC ROD busy caused a lot of downtime• 0.35fb-1 of online data was lost
34
A-side
C-side
2012 pp runs2013 pPb runs
Frequency of ROD busy later 2012
From Masato’s slides: TDAQ Week, 8 July 2013
Analysis Outline
• All the processing done by Reco_trf.py.
RAW data
ESD
AOD
NTUP_SMWZ
NTUP_TRIGMU
ESD
AOD
NTUP_SMWZ
NTUP_TRIGMU
MuonSpectrometer/MuonCnv/MuonTGC_CnvTools/src/TgcRdoToPrepDataTool.h and .cxx were modified.
3 bunch readout 1 bunch readout
35
Modified code to kill hits from adjacent bunches. For MC, run the trigger simulation. Thanks to Susumu Oda for instruction and help.
Compare
Compare
Change in Athena Code To Only Use Current Bunch Hits in TGC
• Data analysis:
– MuonSpectrometer/MuonCnv/MuonTGC_CnvTools/src/TgcRdoToPrepDataTool.cxx• Changed void Muon::TgcRdoToPrepDataTool::selectDecoder(constTgcRdo
::const_iterator& itD, const TgcRdo * rdoColl) to simply return if (*itD->bcTag()=!TgcDigit::BC_CURRENT).
• This change only erases prior and next bunch hits in reconstruction, and the trigger information in the event record is unchanged.
– epp.phys.Kyushu-u.ac.jp/~oda/pukiwiki/index.php?DecodeOnlyCurrentBC
• MC
– MuonSpectrometer/MuonCnv/MuonTGC_CnvTools/src/TGC_RodDecoderReadout.cxx:
• Changed code not to produce TgcRawData object for prior and next bunches.– Also changed MuonRdoToMuonDigitTool::decodeTgc( … ) in
MuonSpectrometer/MuonCnv/MuonByteStreamCnvTest/src/MuonRdoToMuonDigitTool.cxx
• So that it executes collection->push_back(newDigit) only for newDigit->bcTag()==TgcDigit::BC_CURRENT.
• https://www.tsukuba.jp.hep.net/twiki/bin/view/Main/KojiSatoTrigSimKillingAdjacentBunchHits
36
Offline Muon Selection• Following MCP Guidelines.• Analyzed combination of MUID/STACO/MUONS and
CB/CB+ST(/Muons for High Pt Searches).– Results are similar across different muon selection.
• Today, I show results on MUONS, CB selection.
37
MUONS Selection• medium+ selection && !(isStandAloneMuon)• has good ID hits
– nPixHits>0– nSCTHits>4– nSCTHoles<3– n>5&&nTRToutliers<n for 0.1<|eta|<1.9
• with n=nTRToutliers+nTRThits
• |d0_exPV|<1.• |z0_exPV|<10.• Pt>7 GeV
38
from analysis web page
MCP guidelines
TGC Hits in Adjacent Bunches in Data• sl_n variables in NTUP_TRIGMU are zero for prior and
next bunches.
39
tgc_currentBC_sl_n
tgc_priorBC_sl_n tgc_nextBC_sl_n
Prior and next bunch hits are safely killed with 1 bunch readout scheme.
TGC Hits in Adjacent Bunches in MC• TGC_prd_bunch in NTUP_L1TGC.
– 1:prior, 2:current, 3:next bunch.
Prior and next bunch hits are safely killed with 1 bunch readout scheme.
40
Details of trigger muon counting• I simply count the number of EF/L2/L1 or offline CB muons that are
found in the D3PD.• Rejecting multiple entries:
• For trigger muons, I only count one muon when I find multiple muons with .
• I typically find multiple L2 muons pointing to the same direction even after requiring a specific trigger bit.
• I don’t find multiple EF muons pointing to the same direction when I require a specific trigger bit.
• EF– Only counting EF muons associated with CB track. Kinematic
plots are with CB track quantities.• L2
– Only counting combfeature L2 muons.• L1
– For counting, I simply count all L1 muons regardless of associated trigger bit – D3PD doesn’t have trigger bits for each L1 muon. Only have event bit. 41
Trig
ger
Muo
n Y
ield
s (
MC
)•
Onl
y fa
ils t
o fin
d on
e E
F m
uon
for
mu4
T
trig
ger
with
one
bun
ch r
eado
ut.
42
Muon Yields (Data)• #MUONS found in 3512939 Muon stream data events.
3bunch reco, Pt(mu)> 7 GeV/c
1bunch reco , Pt(mu)> 7 GeV/c
3bunch reco , Pt(mu)> 30 GeV/c
1bunch reco , Pt(mu)> 30 GeV/c
Difference=(1bunch-3bunch)/3bunch *100%:
Difference=(1bunch-3bunch)/3bunch *100%:
Difference for Endcap CB
Difference for Endcap CB
44
Muon Yields (Z->mumu MC)• Analyzed 249500 MC events.• No change observed in MUONS CB yield (Pt cut >7 or
>30 GeV).
45
Muon Yields (J/psi->mumu MC)• Analyzed 499000 MC events.• Only <~0.002% change is observed, corresponding to
one muon for Pt>7 GeV MUONS CB selection.
46
Top Related