Heavy Ion DiMuon? Trigger Study

Overall Description of Heavy Ion DiMuon? HLT

DiMuon? HLT Algorithm

• Path Name : HLT_HIDoubleMu
• L1 condition : L1_DoubleMuOpen (Low quality and 2 muons, no pT threshold)
• L1 – L2 : using p-p L1-L2 trigger algorithm

• L3 HI DiMuon? trigger algorithm
  • Investigation on Primary Vertex existence ( ≥ 1 )
  • L2 accepted : number of L2 muon ≥ 2 on L2 Muon Collection
  • Fast Muon Propagation : from Muon station to tracker
  • DiMuon? Seeding
  • Trajectory Building (from outside to inside)
  • DiMuon?’s Vertex finding (if the vertex is found, L3 accepted)

HI MuL3? Timing Summary

Preparation for HI timing study at CMSSW_2_2_9

• new HI MuL3? tag (20090716 updated)
  • V00-03-05 RecoHIMuon?/HiMuTracking
  • V00-03-02 RecoHIMuon?/HiMuSeed
  • V00-02-00 RecoHIMuon?/HiMuPropagator

Timing study tools

• Timing study tools
• hltTimingSummary running at CMSSW_2_2_9
  • ../../../../test/slc4_ia32_gcc345/hltTimingSummary -f -i HLT_Hydjet_MinBias_MuL3_total_27k.root -o outHLTTiming -s -f
  • Timing study results
    • data samples
      • MinBias? : /pnfs/cmsaf.mit.edu/hibat/cms/users/cer/digi2raw_226/startup/PbPb081106_MB/
      • Fixed Impact parameters (fm):
        • B = 00 : /pnfs/cmsaf.mit.edu/hibat/cms/users/cer/digi2raw_226/startup/PbPb081106_000/
        • B = 03 : /pnfs/cmsaf.mit.edu/hibat/cms/users/cer/digi2raw_226/startup/PbPb081106_030/
        • B = 06 : /pnfs/cmsaf.mit.edu/hibat/cms/users/cer/digi2raw_226/startup/PbPb081106_060/
        • B = 09 : /pnfs/cmsaf.mit.edu/hibat/cms/users/cer/digi2raw_226/startup/PbPb081106_090/
        • B = 12 : /pnfs/cmsaf.mit.edu/hibat/cms/users/cer/digi2raw_226/startup/PbPb081106_120/

MinBias? Hydjet HLT_HIDoubleMu Trigger efficiency and rate

Heavy Ion DiMuon? Trigger : HLT_HIDoubleMu at CMSSW_3_1_0 (20090829 updated)

HLT Study Setup

• J/psi sample Generation 30k with jpsi_PtYDisGun_cfg.py (should globalTag : MC_31X_V1::All) jpsi_PtYDisGun_cfg.py (current setup is including Raw step)
• Upsilon sample Generation 30k with upsi_PtYDisGun_cfg.py upsi_PtYDisGun_cfg.py (current setup is including Raw step)
• Digi to Raw :
  • cmsDriver.py RelVal? --step=DIGI,L1,DIGI2RAW --condition=FrontierConditions_GlobalTag,STARTUP_31X::All --number=100 --mc --no_exec --datatier 'GEN-SIM-DIGI-RAW' --eventcontent=FEVT --python_filename=RelVal_Digi_Digi2Raw.py --processName=RAW
  • cmsRun RelVal?_Digi_Digi2Raw.py RelVal_Digi_Digi2Raw.py
• HLT_HIDoubleMu :
  • L3 HI Muon code download
    • cvs co -r V00-03-08 RecoHIMuon?/HiMuTracking
    • cvs co -r V00-03-02 RecoHIMuon?/HiMuSeed
    • cvs co -r V00-02-02 RecoHIMuon?/HiMuPropagator
  • edmConfigFromDB --configName /dev/CMSSW_3_2_2/HIon/V1/ --format Python --paths HLT_HIDoubleMu > HLT_HIDoubleMu.py
  • cmsRun HLT_HIDoubleMu.py HLT_HIDoubleMu.py

Trigger efficiency and rate at CMSSW_2_2_9

• L3/L2 efficiency = 197/370 = 0.53 among 28409 events
• Assuming rate = 197/28409 * 3kHz(8kHz) = 20.7(55.48) Hz

HI TestMuL3? development for whole eta(|eta|<2.4) region with CMSSW_2_2_9 (20090715 updated)

What is the difference between new one and before

• new parmeterization which recalculated at 3.8 T applied >> extend to |eta|<2.4
• modification of navigation school setter >> extend to |eta|<2.4
• new tag
  • V00-03-01 RecoHIMuon?/HiMuSeed
  • V00-02-00 RecoHIMuon?/HiMuPropagator
  • V00-03-01 RecoHIMuon?/HiMuTracking
• 1) Efficiency in Barrel : 70 %(L3/L2), 80 % (L3/(L2+PV)

• 2) Efficiency in Barrel + Endcap : 46 %(L3/L2), 51 % (L3/(L2+PV))

HI TestMuL3? development for Barrel with CMSSW_2_2_9 (20090626 updated)

What is the difference between new one and before

• new parmeterization which recalculated at 3.8 T applied
• modification of navigation school setter
• new tag
  • V00-02-05 RecoHIMuon?/HiMuSeed
  • V00-01-02 RecoHIMuon?/HiMuPropagator
  • V00-02-08-05 RecoHIMuon?/HiMuTracking
• develped from 43 % to 67 % (L3/L2) in the Barrel

HI TestMuL3? new parameterization study with CMSSW_2_2_9

1. Making new parameterization with TestMuL1L2Filter?.cc here(made by Olga)

1) Test with Upsilon 100k events, Gen information

* Upsilons

* Muons from upsilons

2) Test with Upsilon 100k events, new parameterization

* delPhi vs Muon Gen Pt (with color palette) depending on eta region

* delPhi vs Muon Gen Pt (with no color palette) depending on eta region

* Muon pt resolution

First Try to get L3/L2 upsilon trigger efficiency (vs eta & pT) (200903 updated)

* analysis concept

- investigated how many MC upsilons are triggered events,

- trigger condition : the number of muons at one event should be more than 2. And both muons are |eta| < 0.8 or at least one muon are there.

- used analyzer is here L1L2L3HIAnalyzer.cc

-- DongHoMoon - 17 Jun 2009