1 / 47

Muon Reconstruction/Trigger Performance with TGC 1 Bunch Readout Mode

Muon Reconstruction/Trigger Performance with TGC 1 Bunch Readout Mode. Koji Sato MTSG meeting July 21 , 2014. 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. ↓

alesia
Download Presentation

Muon Reconstruction/Trigger Performance with TGC 1 Bunch Readout Mode

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. MuonReconstruction/Trigger Performance with TGC 1 Bunch Readout Mode Koji Sato MTSG meeting July 21, 2014

  2. 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) • I show a study of offline muon properties this time. • How the change affects the trigger is under study.

  3. RunNumber 215473 EventNumber39074754 CAL Burst Event ② TGC + CAL RPC + TGC + CAL MDT + RPC + TGC + CAL From Masato’s slides: TDAQ Week, 8 July 2013

  4. Analyzed Datasets Today, I will show plots showing all the combined muons (EF/L2 and Offline) found in the D3PDs. Run 215433: Nov 30, 2012 Peak lum=6.7e33 IntLum=123 pb-1

  5. Comparison of trigger muons in trigger simulated MC samples

  6. EF muon distributions • Plotting distributions of EF muons with mu6 bit and associated with CB tracks. Blue: 3 bunch readout Red: 1 bunch readout

  7. EF muon distributions • Plotting distributions of EF muons with mu6 bit and associated with CB tracks. Blue: 3 bunch readout Red: 1 bunch readout

  8. 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

  9. L2muon distributions • Plotting distributions of L2 comb muons with mu6 bit. Blue: 3 bunch readout Red: 1 bunch readout

  10. L2 muon distributions Blue: 3 bunch readout Red: 1 bunch readout

  11. 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

  12. L1muon distributions • Plotting L1 muons without requiring trigger bit. • D3PD only contains L1 bit for event. Blue: 3 bunch readout Red: 1 bunch readout

  13. L1 muon distributions Blue: 3 bunch readout Red: 1 bunch readout

  14. Difference in Simulated L1 Trigger Muons, Z->mumu MC • Plotting (1bunch – 3bunch mode) • We expect no difference for L1, since L1 muon trigger only considers Current bunch hits. • Similar results from J/psi sample • No difference in kinematics

  15. 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.

  16. 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.

  17. Offline Reconstructed Muons (Full Stat.) Blue: 3 bunch readout Red: 1 bunch readout • CB muons of MUONS collection, Pt>7 GeV

  18. Offline Reconstructed Muons(small stat.) Blue: 3 bunch readout Red: 1 bunch readout • CB muons of MUONS collection in 1.1<|η|<1.6. MC MC

  19. Offline Reconstructed Muons(small stat.) Blue: 3 bunch readout Red: 1 bunch readout • CB muons of MUONS collection in 1.1<|η|<1.6. MC MC

  20. Offline Reconstructed Muons(small stat.) Blue: 3 bunch readout Red: 1 bunch readout • CB muons of MUONS collection in 1.1<|η|<1.6. MC MC MC MC

  21. Offline Reconstructed Muons(small stat.) Blue: 3 bunch readout Red: 1 bunch readout • CB muons of MUONS collection in 1.1<|η|<1.6. MC MC

  22. Dimuon Mass (Full stat.) Blue: 3 bunch readout Red: 1 bunch readout MC MC

  23. Difference in Offl. Reco Variables, Z->mumu MC • Plotting (1bunch – 3bunch mode)

  24. Difference in Offl. Reco Variables, J/psi->mumu MC • Plotting (1bunch – 3bunch mode)

  25. Difference in Offl. Reco Variables, Data • Plotting (1bunch – 3bunch mode)

  26. Muons of 3 BC scheme matched to 1 BC muon within dR<0.01 Data Pt eta phi author nTGCEtaHits nTGCPhiHits

  27. Muons of 3 BC scheme matched to 1 BC muon within 0.01<dR<0.1 Data Pt eta phi author nTGCEtaHits nTGCPhiHits

  28. Muons of 3 BC scheme having no matched 1 BC muonwithin dR <0.1 Data Pt eta phi author nTGCEtaHits nTGCPhiHits

  29. 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.

  30. 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.

  31. backup

  32. 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

  33. RunNumber 215473 EventNumber39074754 CAL Burst Event ② TGC + CAL RPC + TGC + CAL MDT + RPC + TGC + CAL From Masato’s slides: TDAQ Week, 8 July 2013

  34. TGC problem in 2012 • TGC ROD busy caused a lot of downtime • 0.35fb-1 of online data was lost Frequency of ROD busy later 2012 A-side 2012 pp runs 2013 pPb runs C-side From Masato’s slides: TDAQ Week, 8 July 2013

  35. Analysis Outline Modified code to kill hits from adjacent bunches. For MC, run the trigger simulation. Thanks to Susumu Oda for instruction and help. • All the processing done by Reco_trf.py. RAW data 1 bunch readout 3 bunch readout ESD ESD AOD AOD Compare NTUP_SMWZ NTUP_SMWZ NTUP_TRIGMU NTUP_TRIGMU Compare MuonSpectrometer/MuonCnv/MuonTGC_CnvTools/src/TgcRdoToPrepDataTool.h and .cxx were modified.

  36. Change in Athena Code To Only Use Current Bunch Hits in TGC • Data analysis： • MuonSpectrometer/MuonCnv/MuonTGC_CnvTools/src/TgcRdoToPrepDataTool.cxx • Changed voidMuon::TgcRdoToPrepDataTool::selectDecoder(constTgcRdo::const_iterator& itD, constTgcRdo * 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

  37. 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.

  38. 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 MCP guidelines from analysis web page

  39. TGC Hits in Adjacent Bunches in Data • sl_nvariables in NTUP_TRIGMU are zero for prior and next bunches. tgc_currentBC_sl_n Prior and next bunch hits are safely killed with 1 bunch readout scheme. tgc_nextBC_sl_n tgc_priorBC_sl_n

  40. 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.

  41. 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.

  42. Trigger Muon Yields ( MC) • Only fails to find one EF muon for mu4T trigger with one bunch readout.

  43. Trigger Muon Yields (J/psi MC) • Only fails to find one EF muon for mu4T trigger.

  44. MuonYields (Data) • #MUONS found in 3512939 Muon stream data events. 3bunch reco, Pt(mu)> 7 GeV/c 1bunch reco , Pt(mu)> 7 GeV/c Difference for Endcap CB Difference=(1bunch-3bunch)/3bunch *100%: 3bunch reco , Pt(mu)> 30 GeV/c 1bunch reco , Pt(mu)> 30 GeV/c Difference for Endcap CB Difference=(1bunch-3bunch)/3bunch *100%:

  45. Muon Yields (Z->mumu MC) • Analyzed 249500 MC events. • No change observed in MUONS CB yield (Pt cut >7 or >30 GeV).

  46. Muon Yields (J/psi->mumu MC) • Analyzed 499000 MC events. • Only <~0.002% change is observed, corresponding to one muon for Pt>7 GeVMUONS CB selection.

  47. Time of Flight at TGC location • TGCinnerlayer at R~13 m

More Related