Transcript Document

Report from the Muon Trigger WG
Aleandro Nisati
On behalf of the Muon Trigger Slice
Community
Muon Week, April 18° 2007
Level-1
LVL1 Barrel: Efficiency curves for low-pT
thresholds
Standard low-pT thresholds
(6, 8, 10 GeV/c)
log scale
pT [GeV]
pT [GeV]
• CSC single muons data (Athena release12.0.3)
• LvL1 performances have been studied using
CommonMuonSlice AANT produced with rel 12.0.6
pT [GeV]
LVL1 barrel : Low-pT Trigger rates
Using the Level-1 Efficiency curves we may
estimate the rates with different threshold.
10 GeV
threshold
Lumi=1033
8 GeV
threshold
Lumi=1033
6 GeV
threshold
Lumi=1033
5 GeV
threshold
Lumi=1033
"Cosmic"
threshold
Lumi=1033
/K
b
c
W
5400 Hz
8830 Hz
10470 Hz
21800 Hz
62500 Hz
920 Hz
1160 Hz
1650 Hz
2220 Hz
3360 Hz
510 Hz
660 Hz
970 Hz
1400 Hz
2400 Hz
3 Hz
3 Hz
3 Hz
3 Hz
3 Hz
t
Sum
Negligible
Negligible
Negligible
Negligible
Negligible
6.8 kHz
11 kHz
13 kHz
25.5 kHz
68.3 kHz
Muon
sources
LVL1 Barrel: Efficiency curves for high-pT
thresholds
Standard high-pT thresholds
(11, 20, 40 GeV/c)
log scale
pT [GeV]
pT [GeV]
• CSC single muons data (Athena release12.0.3)
• LvL1 performances have been studied using CommonMuonSlice AANT produced with rel 12.0.6
• High-pT plateau at 78%
LVL1 barrel : High-pT Trigger rates
Ri  L
11 GeV
threshold
Lumi=1034
20 GeV
threshold
Lumi=1034
40 GeV
threshold
Lumi=1034
/K
b
c
7420 Hz
3540 Hz
670 Hz

2330 Hz
760 Hz
280 Hz
1100 Hz
340 Hz
130 Hz
W
t
Sum
28 Hz
26 Hz
23 Hz
Negligible
Negligible
Negligible
12 kHz
4.7 kHz
1.1 kHz
Muon
sources
p T _cutoff

p T _ inf
d i
  (pT ) dpT
dpT
Inclusive μ cross-section @
LHC
(prompt μ and /K decay)
Rate [Hz]
LVL1 barrel : Trigger rates vs. Threshold
The plot shows the
expected single muon
trigger rates at a
luminosity of 1033 cm-2s-1.
The cosmic configuration
is plotted with a threshold
of 3 GeV.
threshold [GeV]
Endcaps : Software Status
Latest TGC(endcap) LVL1 trigger software(towards 13.0.0)
TrigT1TGC-00-01-26
- The algorithm creating CBNTAA is added.
- Some minor bugs are fixed.
TGCcabling-00-00-34
- Bug fixed
Effect of these bugs are negligible.
Future plan (once CBNTAA data is available)
- perform rate calculation with the latest trigger configuration
- optimize coincidence window and investigate position dependency
- more detailed study of LVL1 di-muon trigger.
Endcap Trigger Efficiency
We used these data set.
- Single muon events produced with athena 12.0.3(RDO)
- Use TrigT1TGC-00-01-18-10 for LVL1 trigger simulation
6GeV
20GeV
3-station coincidence
trigger efficiency of TGC
Threshold Plateau
6GeV
80.9% 95.9%
20GeV
94.4% 95.2%
Endcap Trigger Rates
L=1033 cm-2 s-1
L=1034 cm-2 s-1
Muon sources
Threshold =
6 GeV
Threshold =
5 GeV
Threshold =
20 GeV
Threshold =
40 GeV
/K
5.9
??
6.9
3.60
beauty
1.8
??
1.3
0.48
charm
1.0
??
0.7
0.27
W
negligible
negligible
0.04
0.04
top
negligible
negligible
negligible
negligible
total
8.7
??
8.9
4.4
MuCTPI overlap resolution in the endcap
•
We discovered that the sector
numbering in the TGC and
MuCTPI simulations were not
consistent
•
This led to an increased fake
double-count rate, since some
sector edges were not handled
by either simulation.
•
Compensating for it in the
MuCTPI simulation, this is how
the EC double-count
probabilities change.
•
This results in a 315 Hz  37
Hz fake double count rate
reduction in the endcap.
(Preliminary result)
•
The total fake di muon rate goes
from 432 Hz to ~154 Hz
without MuCTPI
with MuCTPI
after the fix
MuCTPI overlap resolution in the
endcap
Overlap type
w/o overlap removal in
MuCTPI
with overlap removal in
MuCTPI
Barrel-Barrel
169 Hz
81 Hz
Barrel-Endcap
174 Hz
8 Hz
Endcap-Endcap
486 Hz*
37 Hz*
Forward-Forward
43 Hz*
28 Hz*
872 Hz
154 Hz
Total
(*) Not using strip masks on sector edges. This may improve the rejection of
double counting.
LVL2 Algorithms
muFast: improvements since last TP week
•
mFast resolution improved by the use of LUT for separate charge;
– 6 GeV resolution moves from 10% to 7%;
•
degradation of the resolution at high-pT due to the vertex spread recovered by the
use of the MDT fit segment from the Innermost Station;
• comparison between mFast resolution
obtained making use of different
reconstructed variables
(alpha and beta angles) shows a similar
behaviour but:

– alpha has more coverage than beta;
– alpha shows less tails in the resolution
distributions
• Studies on which variables is best
to use is still going on;
• Studies to improve the timing of the
calibration access are ongoing too.

DR
muFast: improvements since last TP Week
•
mFast resolution improved by the use of LUT for separate charge;
–
6 GeV resolution moves from 10% to 7%;
•
degradation of the resolution at high-pT due to the vertex spread recovered by the
use of the MDT fit segment from the Innermost Station;
•
•
•
•
•
comparison between mFast resolution
obtained making use of different
reconstructed variables
(alpha and beta angles) shows a similar
behaviour but:
–
–
–
alpha has more coverage than beta;
alpha shows less tails in the resolution
distributions
•
•
Studies on which variables is best
to use is still going on;
•
•
Studies to improve the timing of the
calibration access are ongoing too.


muFast: Using charge dependent LUT
We use a Look-Up Table to calculate
pT from the angle α.
By taking into account the charge
difference in the LUT, we see an
improvement in the overall resolution
~10 %  ~7 %
muFast:Momentum measurement
Sigma of Resolution
distributions
Momentum measurement using
alpha, beta, radius and DeltaR
Performances obtained using
sample with no spread in Z for
primary vertex. (Slight difference in
dataset wrt previous measurement)
As expected momentum
measurement from radius
and deltaR are linear wrt
momentum on large
momentum range.
Mean of Resolution
distributions
Accessing the MDT calibration constants at
LVL2
Problem: Using MDT calibration a` la offline takes ~40%~50% of total muFast
time
First: Understand the best granularity to access the MDT calibration constants
(per tube, per layer, per station,...)
Looking at Sector13 cosmics data (Nov 2006) accessing t0 and r-t relation per MultiLayer
should be good enough (at least for LVL2 trigger purposes )
T0 distribution
~4ns
BIL1
Drift length
~ 7ns
BIL2
BIL3
LVL2 mIsol Status
• Algorithm:
– Included in 13 nightlies
– Migration to new steering:done
– Configurables migration: on going (ready in 1 week)
• Monitoring:
– new monitoring module added: AANT + Histograms
– so far used for CSC studies, eventually will provide monitoring
histograms for DQ
• Performances/Optimization studies:
– Just started:
• timing  cones/cell energy threshold optimization
– To follow:
• efficiency for Z/Wmmm, rejection against bbmX BG
Event Filter
TrigMoore : Brief Reminder (12.0.6)
Two different running modes:
LVL1
Seeded
Reconstruction performed only in the geometrical
regions provided by the RoIs of previous levels.
LVL2 (muFast)
Full scan
Full reconstruction, ~equivalent to the offline
LVL2 (muComb)
working mode
•
•
•
•
•
Seeding Algs
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
Moore Algs
steering, for reconstruction in the MS,
extrapolation to the IP and combination
with ID tracks
TrigMoore attaches to the TE a
TrigMoore
MuIdStandAlone
"TrigMooreFeature" for each ROI,
Algs
accessed by TrigMooreHypo for pT test
TrigMoore records in SG the
TrigMooreFeature per each ROI and all
MuIdCombined
reconstructed tracks in the event in a
Algs
single container for conversion in
Trk:Track format and subsequent output
Offline ID
in ESD and AOD
LVL2 ID
Hypo Alg
Hypo Alg
Hypo Alg
Work Ongoing for Rel 13
• TrigMoore and TrigMooreHypo have been migrated to the new
trigger steering
– first validation OK; more robustness test will follow
• Use of the configurables
• EDM Migration (see next slides)
• Use of HLT seeded New Tracking ID for combined muons in
TrigMuidCombined (see next slides)
• Ongoing work to increase modularity:
– present implementation not very flexible
– we’ll have 3 HLTalgos instead of 3 instances of TrigMoore
EDM Migration
• Need to adapt Moore to be able to easily use new pattern recognition algs
– Cosmic pattern recognition
– Local CSC and MDT tracking
– to be able to easily output objects required for Calibration/Alignment studies
– use of PRD as common input
• Motivated by Common Tracking for ATLAS and by desire for increased
commonality in Muon-specific reco software
• The current (12.0.6) implementation of TrigMoore uses digits (RDO) as input
objects. Standard muon-sw converters or the production of digits from
(transient) byte-stream or from RDO are used. Need to use Muon
PrepRawData as input.
(Trig)Moore
PhiPatternsAlgTool
Phi Patterns
RZ Patterns
RZPatternsAlgTool
Combine
Patterns
Calibrated
Segments
Combined
Segments
Roads
Trigger rates
First exercise to look at rates at pT thresholds different than
the typical scenarios: 6 and 20 GeV/c Luminosity set to 1033 cm-2s-1
efficiencies for LVL1
from F. Conventi for
6, 8, 10 GeV/c
(in good agreement with
our estimates)
our estimates for
11, 20, 40 GeV/c
Typical scenarios:
mu(6)
3.0 kHz
mu(20) 25 Hz
Trigger rates
First exercise to look at rates at the EF in the END CAPS
and vs pT thresholds
Luminosity set to 1033 cm-2s-1
Efficiencies for LVL1
from our estimate
maybe slightly
inaccurate for the
known bugs in
TGCCabling
expected effects at EF <10%
Typical scenarios:
mu(6)
3.1 kHz
mu(20) 27 Hz
Barrel + EndCap EF Rate @ 1033 cm-2s-1
mu(6) 6.1 kHz
mu(20) 52 Hz
Trigger Rates
Rate for mu(5) at the EF in the barrel
use LVL1 efficiency for the barrel with the trigger
re-configured to have 5GeV/c as lowest threshold
Luminosity set to 1033 cm-2s-1
Muon
sources
/K
b
c
W
t
Total
5 GeV/c
threshold
kHz
6 GeV/c
threshold
kHz
5.0
1.9
1.2
0.67
0.65
0.34
0.003
0.003
negligible negligible
6.9 kHz
3.0 kHz
Muon Slice Data Quality (II)
• Nothing exists for the moment for Muon Slice DQA but
what implemented for monitoring during 2004 test beam (A. Di Mattia for LVL2) and
the test of the trigger slices on the pre-series machines at Point 1 in december 2006
(D. Scannicchio for EF) can be a starting point for Data Quality Monitoring
e.g. MuFast histos from last technical run
Trigger/TrigAlgorithms/TrigmuFast/src/OnlineSurvey.cxx
Shows linear distribution
between 1/s and pT as
expected
Core of the fit residual matching
the resolution of the single tube:
80 mm.
Muon Slice Data Quality (III)
e.g. TrigMoore histos for the ongoing 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)