event filter and trigger menu l=10 31 cm -2 s -1 sergio grancagnolo on behalf of the muon trigger...
TRANSCRIPT
Event Filter and Trigger MenuL=1031cm-2s-1
Sergio Grancagnolo
on behalf of the Muon Trigger software group
Outline• News on EF algorithm implementation (for
rel. 13.x.x)
• HLT Data Quality assessment
• EF performance studies– resolution/efficiency– EF rates – status of the studies of muons from decay
• Muon trigger rates and trigger menu for LHC startup
Two different running modes:SeededSeeded
Reconstruction performed only in the geometrical regions provided by the RoIs of previous levels.
Full scanFull scanFull reconstruction, ~equivalent to the
offline working mode
LVL2 (muFast)LVL2 (muFast)
Moore AlgsMoore Algs
LVL1LVL1
MuIdStandAloneMuIdStandAloneAlgs Algs
TrigMooreTrigMoore
Seeding AlgsSeeding Algs
MuIdCombinedMuIdCombinedAlgs Algs
Hypo AlgHypo Alg
Hypo AlgHypo Alg
Hypo AlgHypo Alg
TrigMoore – a reminder
Seeding Algorithms assume the seed is from LVL2 or a LVL1 ROI
• Full functionality in barrel and end-caps
• 3 istances of TrigMoore called by the steering, for reconstruction in the MS, extrapolation to the IP and combination with ID tracks
• TrigMoore attaches to the TE a "TrigMooreFeature" for each ROI, accessed by TrigMooreHypo for pT test
• TrigMoore records in SG the TrigMooreFeature per each ROI and all reconstructed tracks in the event in a single container for conversion in Trk:Track format and subsequent output in ESD and AOD
LVL2 (muComb)LVL2 (muComb)
LVL2 IDLVL2 ID
Offline IDOffline ID
MuonEF in Rel 13.0.10• Migration to new HLT Steering (DONE)
– Both FEX and Hypothesis algorithms
• Migration to Configurables (DONE)– TrigMoore configurables py classes available in 3 flavours
(MuonSpectrometer, Extrapolated and Combined Tracks)– New style EF muon sequences (including ID) added in
TrigHypothesis/TrigMuonHypo
• Migration to new EDM (DONE)– TrigMoore uses the standard reconstruction input object
(PrepRawData).– The Moore offline algorithm organization has been adopted also by
TrigMoore
• Use of EF version of ID for combined MS-ID tracks (DONE)– MuidCombined adapted to get as input EF-ID tracks.– Replacement of the previous implementation in wich EF ID and offline ID
(New Tracking or iPatRec) was used.
MuonEF in Rel 13.0.10• Implementation of REGTESTs for Monitoring and Validation
(DONE)• Monitoring Histo in Hypo Algo (DONE)• Definition of jobOptions to include Muon EF in ATN test
(DONE)• Bug Fix- Fix for duplicated python modules in genConf (DONE-
to be collected right after 13.0.10)• Bug Fix- Problem in Persistification (appeared in 13.0.X nightly)
Fixed in 13.0.10
Muon HLT Data Quality
Preliminary considerations on DQ monitoring and assessment for the muon slice presented at TDAQ Data Quality Wshop in Zeuthen (February 28-March 1 2007), focusing on LVL2 and EF, in online/offline
e.g. for EF online monitoring:
• hit #/track per tecnology;• geometrical track
parameters;• pt spectrum;• track quality (2);
Muon Slice Data Quality (I)Muon Slice Data Quality (I)
• residual distributions;• matching with ID;• combined tracks/moore tracks;• ratio of positive/negative tracks;• matched hits/total hits in the seed
region;
Monitoring activities are going to be organized for LVL1/2/3 in the appropriate environments, to use general tools and DQ Monitoring framework, to move the first steps towards muon trigger slice DQ
Nothing exists for the moment for Muon Slice DQA but what implemented for monitoring during 2004 test beam (for LVL2) and the test of the trigger slices on the pre-series machines at Point 1 in december 2006 (for EF) can be a starting point for
Data Quality Monitoring
e.g. TrigMoore histos from the last technical run
Trigger/TrigAlgorithms/TrigMoore/src/TrigMooreHisto.cxx
(here obtained running the jobOptions prepared for the on-line with a bytestream file containing 50 top events as input: muons are selected by the LVL2 and the EF muon algorithms)
Muon Slice Data Quality (II)Muon Slice Data Quality (II)
completed in release 13 for TrigMoore Hypothesis algos
EF Performance studies
Sample and releases• Single mu sample centrally simulated on lcg-dq grid (CSC
production)– mixed charge; – pT from 2 to 200 GeV/c– total statistics ……
• Reconstruction with a dedicated sw chain in 12.0.6– Muon Trigger slice only
• LVL1 emulation, (100% of the statistics processed with standard LVL1 configuration, part of the low pt points re-processed with low thresholds)
• LVL2: mufast, IDscan, muComb• EF(seeded by LVL2): trigmoore + EF ID algo• Hypothesis algorithms disabled
– Private AA NTuple production using grid tools (GANGA) on Napoli Tier2 storage elements (mostly by Napoli group)
– Used for both LVL1 (Napoli, Tokyo) and EF (Lecce, Napoli) studies– Main goal: CSC note
efficiency, resolution, single muon trigger rates
Efficiency and resolution curves (standard LVL1 configuration)
barrel EF MuId Combined efficiency curves w.r.t. LVL2
(muComb)
pT (GeV)
6 GeV 8 GeV
20 GeV 40 GeV
pT (GeV)
barrel EF resolutions
MuidStandAloneTrigMooreMuidCombined
EF MuId Combined Resolutions
Endcap Overlap
Very Fwd All
Other EF Muon Trigger ratesOther EF Muon Trigger rates6 GeV
1033cm-2s-1
Barrel
(Hz)
Endcap
(Hz)
beauty 641 845
charm 327 426
top 0.05 0.07
W 2.9 4.0
/K 1918 1462
TOTAL 2889 2737
8 GeV 1033cm-2s-1
Barrel
(Hz)
Endcap
(Hz)
beauty 172 291
charm 77 134
top 0.06 0.05
W 2.8 3.9
/K 281 313
TOTAL 533 742
20 GeV 1034cm-2s-1
Barrel
(Hz)
Endcap
(Hz)
beauty 73 118
charm 28 46
top 0.27 0.32
W 22.3 32.6
/K 50 48
TOTAL 173 244
40 GeV 1034cm-2s-1
Barrel
(Hz)
Endcap
(Hz)
beauty 2.5 4.5
charm 0.87 1.6
top 0.07 0.07
W 3.9 7.1
/K 0.2 0.3
TOTAL 7.5 13.6
EF Efficiency curves (for low pt regime)
EF (MuId CB) efficiency w.r.t. LVL2 (muComb)
3 5 3 5pT (GeV) pT (GeV)
pT threshold at 4 GeV corresponds to a totally open LVL1 window – EF effective threshold is 3 GeV/cpT threshold at 5 GeV has a cut lowered by 2 times the resolution corresponding at 5 GeV (as for higher thresholds)
“4 GeV” 5 GeV
barrel barrel
Low pT thresholds single muon rates
“4 GeV” 1031cm-2s-1
Barrel
(Hz)
Endcap
(Hz)
/K 133 80
beauty 19 21
charm 11 12
top 6∙10-4 8∙10-4
W 0.03 0.04
TOTAL 163 113
5 GeV 1031cm-2s-1
Barrel
(Hz)
Endcap
(Hz)
/K 44 30
beauty 11 13
charm 6 7
top 5∙10-4 7∙10-4
W 0.03 0.04
TOTAL 61 49
Luminosity: L = 1031cm-2s-1
Trigger Menus Proposal for L=1031 cm-2s-1
L1 trig. item Rate LVL2 Rate EF Rate
MU4 ~1 kHz
μComb TrigMoore
TrigDiMuon DiMuon
PS/PT 1 Hz PT 1 Hz
MU6 227 Hz
μComb 80.8 Hz TrigMoore 56.3 Hz
InDet only PS/PT
μFast only 99.7 Hz PS/PT
PS/PT 1 Hz PT 1 Hz
MU10 112 HzμComb TrigMoore ~10 Hz
PS/PT 1 Hz PT 1 Hz
Trigger Menus Proposal for L=1031 cm-2s-1
L1 trig. item Rate LVL2 Rate EF Rate
MU15 19 Hz
μComb TrigMoore ~2 Hz
InDet only PT
μFast only PT
PS/PT 1 Hz PT 1 Hz
MU20 14 Hz PT 14 Hz PT 14 Hz
MU40 8 Hz PT 8 Hz PT 8 Hz
2MU4 ~9 Hz ??? PT
2MU6 4 Hz PT 4 Hz PT 4 Hz
2MU10 ~1 Hz PT ~1 Hz PT ~1 Hz
2MU20 < 1 Hz PT < 1 Hz PT < 1 Hz
2MU40 < 1 Hz PT < 1 Hz PT < 1 Hz
Expre
ss s
tream
s
Trigger efficiency from Z → μ+μ-
Double Object (DO) method
1-2 % statistical uncertainty with few pb-1 dataDifferential (η,φ) trigger efficiency determinationCSC AOD analysis is going to be finalized
Double Object with orthogonal Signature (DOS) method
Backgrounds from BBμμX, Wμv, Zττ Different reconstruction modes
Muons from /K
Strategy
• extract from minimum bias and dijets of various energy a global pT vs distribution for pions and kaons, re-weighting to a common value of the integrated luminosity
• Use the particle-generator to generate single pions according to the previous distribution
• simulate the decay of pions with G4 saving only events were the pion decay before the muon spectrometer
• study a procedure to identify and reject this kind of muons
Event SampleEvent
SampleFile Name Events
Cross Section (mb)
minimum bias
csc11.005001.pythia_minbias.evgen.EVNT.v11004202._xxxxx 124200 92E00
J1 csc11.005010.J1_pythia_jetjet.evgen.EVNT.v11004201._xxxxx 242287 1.376E00
J2 csc11.005011.J2_pythia_jetjet.evgen.EVNT.v11004201._xxxxx 257508 9.327E-02
J3 csc11.005012.J3_pythia_jetjet.evgen.EVNT.v11004201._xxxxx 30299 5.884E-03
J4 csc11.005013.J4_pythia_jetjet.evgen.EVNT.v11000401._xxxxx 40400 3.084E-04
J5 csc11.005014.J5_pythia_jetjet.evgen.EVNT.v11000401._xxxxx 5050 1.247E-05
J6 csc11.005015.J6_pythia_jetjet.evgen.EVNT.v11000401._xxxxx 50000 3.604E-07
J7 csc11.005016.J7_pythia_jetjet.evgen.EVNT.v11004201._xxxxx 5050 5.707E-09
J8 csc11.005017.J8_pythia_jetjet.evgen.EVNT.v11004201._xxxxx 10100 2.444E-11
Particle selection requiring:
• PDG code • ||<2.7
• pT>500MeV • generation at the interaction point (0.,0.,0.)
and filling a two-dimensional histogram of pT vs , one entry for each pion.
pT vs distributionsMinimum bias
Dijets J8
Some existing correlation between pT and requires a generation according to the 2-D distribution
The solution that I adopted is to slice the 2-D histograms in pT bins and simulate using the 1-D projections in pT and
A tool was developed to force all the generated pions to decay:
the PionDecayer
Supposing an efficiency =10-4 between 2.5 GeV and 7.5 GeV, and a granularity of 500 MeV, to extimate an error of 10% 106 events needed in each bin
If only ~1% of the pions decays in the volume before the calorimeter
at least 109 events should be generated
The red curve, mu6 eff. at EF, is estimated with 10 pT points (2GeV/c – 8 GeV/c) with 106 – 0.5·106 single muon each but events passing LVL2 are 30 at 3 GeV/c, 500 at 4 GeV/c, 3600 at 5 GeV/c, 350k at 6 GeV/c
Single muon efficiency
Produced sample• no available tools to randomly extract from a 2D
distribution– solution: slice the 2D distribution in pt bins (of ~same content)
and generate according to the 1D distributions of pT and Eta
• From PANDA, centrally simulated files:Task name Task IDReq JobsDone JobsTotal events Prio GridStatus Timestampmisal1_mc12.007180.singlePion_pTSlice_20_of_30.digit.v12000502 7822 500 500 25000 100 osg done Apr 18 10:04misal1_mc12.007162.singlePion_pTSlice_2_of_30.digit.v12000502 6296 1600 1600 80000 100 osg done Mar 1 12:34misal1_mc12.007163.singlePion_pTSlice_3_of_30.digit.v12000502 6295 1400 1400 70000 100 osg done Mar 1 12:33………misal1_mc12.007189.singlePion_pTSlice_29_of_30.digit.v12000502 6270 100 100 5000 100 osg done Mar 1 11:46misal1_mc12.007190.singlePion_pTSlice_30_of_30.digit.v12000502 6269 100 100 5000 100 osg done Mar 1 11:45
TOTAL: 25.800 files 1.065.000 events ~1.7Tb
pLM
LpP ),(Since, for a given pion direction, the decay is forced into a definite path length L, the single event probability is
Following steps…• Since full statistics has become available all efforts have been directed
to apply the muon slice and the standard ntuple analysis to the single sample– with some addition specific to the case
• keep track of the muon mother and its decay vertex• keep track of the links between a combined reconstructed muon and its ID and
MS seeds, etc...)• Fixes made by Alan and migration of methods from MuidMatch to MuidTrack
• first attempt:– copy from osg grid to castor, submit jobs to lxplus queues for running the
specific reconstruction + analysis code turned out to be unaffordable mostly due to castor access too slow and unstable
• use of grid infrastructures absolutely necessary !– the solution: use lcg-dq after replicating the files to Napoli tier-2
• affordable but still very time consuming;• copy from castor to NA tier-2 took 4/5 days only for higher pT slices (20-30)
– reconstruction jobs submitted on a small part of these replicas• A long process for the study of a critical issue: now all necessary input
ready to perform the analysis and get some results
Problems
• Many problems encountered to complete the analysis chain:– Last simulation job finished ~ half april– Copy output to castor from US grid ~1 week– Many attempts to run the muon trigger slice
• Run athena jobs directly on castor failed• Copy from castor to local nfslocal disk failed• Replicate from castor to european gridongoing• Running muon trigger sliceongoing• Run analysis macroongoing
Conclusions
• Many important steps since last T&P week
• Performances under control
• Data quality and trigger menus under study
• Still waiting to finish the study on muons from single pion sample, but many technical problems– grid tools are already very important
• Stay tuned for new results on this topic