Presentation on theme: "Muon Reconstruction/Trigger Performance with TGC 1 Bunch Readout Mode Koji Sato MTSG meeting July 21, 2014 1."— Presentation transcript:
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 Datasets Dataset name# eventsSimulated for 1 bunch readout datadata12_8TeV.00215433.physics_Muons.merge.RAW 5,869,910Offline reco mc12_8TeV.147807.PowhegPythia8_AU 2CT10_Zmumu.recon.RDO.e1852_a220 _a225_tid01403231_00 249,500Trigger sim Offline reco mc12_8TeV.208002.Pythia8B_AU2_CTE Q6L1_pp_Jpsimu6mu6.recon.RDO.e133 1_a159_a190 499,000Trigger sim Offline 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.
COMPARISON OF TRIGGER MUONS IN TRIGGER SIMULATED MC SAMPLES 5
EF muon distributions Plotting distributions of EF muons with mu6 bit and associated with CB tracks. Blue: 3 bunch readout Red: 1 bunch readout 6
EF muon distributions Plotting distributions of EF muons with mu6 bit and associated with CB tracks. 7 Blue: 3 bunch readout Red: 1 bunch readout
Difference in Simulated EF Trigger Muons, Z->mumu MC Similar results from J/psi sample No difference in # EF muons Very slight change in kinematics for few events 8
Difference in Simulated L1 Trigger Muons, Z->mumu MC 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
COMPARISON OF OFFLINE RECONSTRUCTION Previous 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
Muons of 3 BC scheme matched to 1 BC muon within dR<0.01 Pt eta phi author nTGCEtaHits nTGCPhiHits Data 26
Muons of 3 BC scheme matched to 1 BC muon within 0.01
"name": "Muons of 3 BC scheme matched to 1 BC muon within 0.01
Muons of 3 BC scheme having no matched 1 BC muon within dR <0.1 Pt eta phi author nTGCEtaHits nTGCPhiHits Data 28
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 runs 2013 pPb runs 2013 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
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).TgcRdo 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?DecodeOnlyCurrentBCepp.phys.Kyushu-u.ac.jp/~oda/pukiwiki/index.php?DecodeOnlyCurrentBC MC –MuonSpectrometer/MuonCnv/MuonTGC_CnvTools/src/TGC_RodDecoderReadout.cx x: Changed code not to produce TgcRawData object for prior and next bunches. –Also changed MuonRdoToMuonDigitTool::decodeTgc( … ) in MuonSpectrometer/MuonCnv/MuonByteStreamCnvTest/src/MuonRdoToMuonDigitToo l.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/KojiSatoTrigSimKillingAdjacentBun chHitshttps://www.tsukuba.jp.hep.net/twiki/bin/view/Main/KojiSatoTrigSimKillingAdjacentBun chHits 36
MUONS Selection medium+ selection && !(isStandAloneMuon) has good ID hits –nPixHits>0 –nSCTHits>4 –nSCTHoles<3 –n>5&&nTRT outliers 7 GeV 38 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
Your consent to our cookies if you continue to use this website.