AtlasPublicTopicHeader.png

L1 Muon Trigger Public Results

Introduction

Approved plots that can be shown by ATLAS speakers at conferences and similar events. Please do not add figures on your own. Contact the responsible project leader in case of questions and/or suggestions. Follow the guidelines on the trigger public results page.

Performance plots for Phase-I upgrades

Charge identification performance of the Level-1 endcap muon trigger in Run 3: ATL-COM-DAQ-2019-086 (08 July 2019)

The figure shows the efficiency of the Level-1 endcap muon trigger with 4 GeV of pT threshold (L1_MU4) expected in Run 3 (Red). The L1_MU4 is the lowest threshold muon trigger in Run 2, which has been primarily used for the flavour physics at the ATLAS experiment. The efficiency was estimated by using single-muon simulation with a flat distribution of η and φ. The figure also shows the efficiency of L1_MU4 with correct charge identified by bending direction in the magnetic field (Blue). The accuracy of muon charge identification gets worse with increasing pT. The trigger candidate is masked at small regions (about 2%) of weak magnetic field, similar to 20 GeV threshold applied in Run 2, since muons passing at such weak magnetic field regions are not bent enough.

.png
png pdf eps
contact: Hiroaki Hibi & Junpei Maeda

Performance estimation of the Level-1 Endcap muon trigger at Run 2 and Run 3: ATL-COM-DAQ-2018-033 (27 May 2018)

The pseudo-rapidity (η) distributions of the Level-1 MU20 RoI. The L1 MU20 candidates in Run 2 are collected by pass-through triggers (HLT_noalg_L1MU20), in 2017 data with a center-ofmass energy of 13 TeV and a bunch-crossing interval of 25 ns. The distribution when enabling TileCal-TGC coincidence is estimated from 2017 data. The expected distribution in Run 2 shows the final distribution at the end of Run 2 after enabling TileCal coincidence. Matching between the offline muon and the L1 MU20 RoI requires dR < 0.1, where dR is calculated from dη, dφ between the offline muon position extrapolated to RoI plane and the central position of the RoI. .png
png pdf eps
contact: Shunichi Akatsuka, Yuta Okazaki, & Junpei Maeda
The pseudo-rapidity (η) distributions of the Level-1 MU20 RoI. The L1 MU20 candidates in Run 2 are collected by pass-through triggers (HLT_noalg_L1MU20), in 2017 data with a center-ofmass energy of 13 TeV and a bunch-crossing interval of 25 ns. The distribution when enabling TileCal-TGC coincidence is estimated from 2017 data. The distributions when enabling RPC BIS7/8 and NSW coincidence are estimated from MDT segments information and single muon MC study results. The expected distribution in Run 3 shows the final distribution in Run 3 after enabling all TileCal, RPC BIS7/8, and NSW coincidences. Matching between the offline muon and the L1 MU20 RoI requires dR < 0.1, where dR is calculated from dη, dφ between the offline muon position extrapolated to RoI plane and the central position of the RoI. .png
png pdf eps
contact: Shunichi Akatsuka, Yuta Okazaki & Junpei Maeda

Performance estimation of the Level-1 Endcap muon trigger by using NSW angle information: ATL-COM-DAQ-2017-022 (May 6, 2017)

Distributions of difference in η between the Level-1 Region of Interest (RoI) in the TGC Big Wheel (BW) and the track segment position in the New Small Wheel (NSW), and dθ measured at NSW. dθ is defined as dθ = θposition - θtrack, where θposition is the polar angle calculated from the position of the track segment, and θtrack is the polar angle of the track vector. The distributions are obtained by simulation with muon pT = 20 GeV (left), 40 GeV (right). Two peaks are observed in the left figure (pT= 20 GeV) due to the different charges of the muons. In the right figure (pT = 40 GeV), because the pT of the muons are higher, the split of the two peaks are smaller, and therefore they are not resolved.
.png
png pdf eps
.png
png pdf eps
contact: Shunichi Akatsuka & Junpei Maeda
Relative trigger efficiencies compared to Run-2 Level-1 trigger for a single muon with transverse momentum above 20 GeV (L1_MU20), at 1.3 < |ηRoI| < 2.4. The Run-2 L1_MU20 requires position matching of TGC Big Wheel (BW) and the TGC Forward-Inner chamber (FI) at 1.3 < |ηRoI| < 2.4. The efficiencies are measured with offline reconstructed muons, and are shown as a function of the transverse momentum of the muons. Efficiencies with additional coincidence requirements applied to the L1_MU20 are shown by coloured points. The open circle points show the efficiency with New Small Wheel (NSW) coincidence logic using dη-dθ coincidence window, described in ATL-COM-DAQ-2015-142. The open triangle points show the efficiency with NSW coincidence logic using both dη-dφ and dη-dθ coincidence window derived from the simulation study. The track segment finding efficiency in the NSW is assumed to be 97%. .png
png pdf eps
contact: Shunichi Akatsuka & Junpei Maeda
pT distributions of offline reconstructed muons matched to a Level-1 trigger for a single muon with transverse momentum above 20 GeV (L1_MU20), at 1.3 < |ηRoI| < 2.4. Matching between the offline muon and the L1_MU20 RoI requires dR < 0.5, where dR is calculated from η, φ of the offline muon at I.P. and the central position of the L1_MU20 RoI. The distribution of Run-2 L1_MU20 candidates, generated by the TGC Big Wheel (BW) and TGC Forward-Inner chamber (FI), are collected by pass-through triggers (HLT_noalg_L1MU20), in 2016 data with a center-of-mass energy of 13 TeV and a bunch-crossing interval of 25 nsec. The distributions when including each New Small Wheel (NSW) coincidence logics are estimated by multiplying the relative trigger efficiencies measured by simulation. .png
png pdf eps
contact: Shunichi Akatsuka & Junpei Maeda

Performance estimation of Level1 endcap muon trigger for Run3: ATL-COM-DAQ-2015-142 (September 20, 2015)

Distributions of position differences between the Level-1 Region of Interest (RoI) in the TGC Big Wheel (BW) and track segments in the New Small Wheel (NSW). The distributions are obtained by simulations with muon pT = 20 GeV (top), 40 GeV (bottom). Two peaks are observed in the distribution with muon pT = 20 GeV since the position differences depend on muon’s charge. Criteria of the position matching between the BW-RoI and NSW-track for the Level-1 endcap muon trigger for Run3 are defined from these distributions. .png
png eps
.png
png eps
contact: Tomoe Kishimoto
L1_MU20 trigger efficiencies when including the TGC Forward Inner station (FI) or New Small Wheel (NSW) with respect to the trigger efficiency of the TGC Big Wheel (BW) standalone. The track segment finding efficiency in the NSW is assumed to be 97%. L1_MU20 is a Level-1 trigger for a single muon with transverse momentum above 20 GeV. The trigger efficiencies are measured with offline reconstructed muons with 1.3 < |eta| < 2.5, and shown as a function of the transverse momentum of the muons. During Run1, only TGC BW was used to generate the Level-1 endcap muon triggers. In Run3 (Run2), a coincidence with NSW (TGC FI) will be introduced to reduce the trigger rate. .png
png eps
contact: Tomoe Kishimoto
pT distributions of offline reconstructed muons with 1.3 < |eta| < 2.5 matched to a L1_MU20 candidate. L1_MU20 is a Level-1 trigger for a single muon with transverse momentum above 20 GeV. The distribution with L1_MU20 candidates generated by the TGC Big Wheel (BW) standalone are obtained from a data sample collected by pass-through triggers (HLT_noalg_L1MU20) in run276329, which was taken on 16-17 Aug. 2015 with a center-of-mass energy of 13 TeV and a bunch-crossing interval of 25 nsec. The distributions when including the TGC Forward Inner station (FI) or New Small Wheel (NSW) are estimated by multiplying the relative trigger efficiencies measured by simulations. During Run1, only TGC BW was used to generate the Level-1 endcap muon triggers. In Run3 (Run2), a coincidence with NSW (TGC FI) will be introduced to reduce the trigger rate. .png
png eps
contact: Tomoe Kishimoto

Run 2 performance summary

Summary of level-1 endcap muon trigger in Run 2: ATL-COM-DAQ-2019-021 (22 February 2019)

The figure shows the efficiencies for level-1 single-muon triggers as a function of the transverse momentum of the reconstructed muon in the endcap region, 1.05<|ημ|<2.4 in data 2015. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events. The notation, L1_MU, is the name of level-1 single muon trigger menu at ATLAS, and the last digit corresponds to a threshold of transverse momentum in GeV for muons. The trigger requirements are tightened for higher pT threshold triggers in the endcap region, in addition to tighter pT threshold. L1_MU6 starts using three-station coincidence while L1_MU4 still uses two-station coincidence. L1_MU15 and L1_MU20 use additional coincidence with the TGC inner station. Additionally, events are rejected for small regions where the trigger rate is very high due to a poor magnetic field. .png
png pdf eps
contact: Masato Aoki
The figure shows the efficiencies for level-1 single-muon triggers as a function of the transverse momentum of the reconstructed muon in the endcap region, 1.05<|ημ|<2.4 in data 2016. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events. The notation, L1_MU, is the name of level-1 single muon trigger menu at ATLAS, and the last digit corresponds to a threshold of transverse momentum in GeV for muons. The trigger requirements are tightened for higher pT threshold triggers in the endcap region, in addition to tighter pT threshold. L1_MU6 starts using three-station coincidence while L1_MU4 still uses two-station coincidence. L1_MU15 and L1_MU20 use additional coincidence with the TGC inner station. Additionally, events are rejected for small regions where the trigger rate is very high due to a poor magnetic field. .png
png pdf eps
contact: Masato Aoki
The figure shows the efficiencies for level-1 single-muon triggers as a function of the transverse momentum of the reconstructed muon in the endcap region, 1.05<|ημ|<2.4 in data 2017. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events. The notation, L1_MU, is the name of level-1 single muon trigger menu at ATLAS, and the last digit corresponds to a threshold of transverse momentum in GeV for muons. The trigger requirements are tightened for higher pT threshold triggers in the endcap region, in addition to tighter pT threshold. L1_MU6 starts using three-station coincidence while L1_MU4 still uses two-station coincidence. L1_MU15 and L1_MU20 use additional coincidence with the TGC inner station. Additionally, events are rejected for small regions where the trigger rate is very high due to a poor magnetic field. .png
png pdf eps
contact: Masato Aoki
The figure shows the efficiencies for level-1 single-muon triggers as a function of the transverse momentum of the reconstructed muon in the endcap region, 1.05<|ημ|<2.4 in data 2018. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events. The notation, L1_MU, is the name of level-1 single muon trigger menu at ATLAS, and the last digit corresponds to a threshold of transverse momentum in GeV for muons. The trigger requirements are tightened for higher pT threshold triggers in the endcap region, in addition to tighter pT threshold. L1_MU6 starts using three-station coincidence while L1_MU4 still uses two-station coincidence. L1_MU15 and L1_MU20 use additional coincidence with the TGC inner station. Additionally, events are rejected for small regions where the trigger rate is very high due to a poor magnetic field. .png
png pdf eps
contact: Masato Aoki
The figures show the trigger efficiencies of level-1 single-muon triggers for a threshold of (a) 4 GeV and (b) 20 GeV as a function of the transverse momentum of the reconstructed muon in the endcap region, 1.05<|ημ|<2.4, for different years in Run 2. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events. The turn-on region was optimized for the 20 GeV-threshold trigger at the beginning of 2017 data-taking. Beside the turn-on optimization, the efficiency of the L1 muon endcap trigger has been stable through Run 2. The slight degradation of the plateau efficiency is caused by the increase in the number of disabled detector channels due to high voltage problems.
.png
(a): png pdf eps
.png
(b): png pdf eps
contact: Masato Aoki
The figures show the trigger plateau (offline muon pT > 25 GeV) efficiencies of level-1 single-muon triggers for a threshold of (a) 4 GeV and (b) 20 GeV on the right as a function of azimuthal angle of reconstructed muon in the endcap region, 1.05<|ημ|<2.4, for different years in Run 2. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events. The efficiency of the L1 muon endcap trigger has been stable through Run 2.
.png
(a): png pdf eps
.png
(b): png pdf eps
contact: Masato Aoki
The figures show the trigger plateau (offline muon pT > 25 GeV) efficiencies of level-1 single-muon triggers for a threshold of (a) 4 GeV and (b) 20 GeV on the right as a function of pseudo-rapidity, eta, of reconstructed muon for different years in Run 2. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events. The efficiency of the L1 muon trigger has been stable through Run 2.
.png
(a): png pdf eps
.png
(b): png pdf eps
contact: Masato Aoki
The figures show the trigger plateau (offline muon pT > 25 GeV) efficiencies of level-1 single-muon triggers for a threshold of (a) 4 GeV and (b) 20 GeV in two-dimensional plane of muon track eta and phi. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events in data 2015.
.png
(a): png pdf eps
.png
(b): png pdf eps
contact: Masato Aoki
The figures show the trigger plateau (offline muon pT > 25 GeV) efficiencies of level-1 single-muon triggers for a threshold of (a) 4 GeV and (b) 20 GeV in two-dimensional plane of muon track eta and phi. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events in data 2016.
.png
(a): png pdf eps
.png
(b): png pdf eps
contact: Masato Aoki
The figures show the trigger plateau (offline muon pT > 25 GeV) efficiencies of level-1 single-muon triggers for a threshold of (a) 4 GeV and (b) 20 GeV in two-dimensional plane of muon track eta and phi. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events in data 2017.
.png
(a): png pdf eps
.png
(b): png pdf eps
contact: Masato Aoki
The figures show the trigger plateau (offline muon pT > 25 GeV) efficiencies of level-1 single-muon triggers for a threshold of (a) 4 GeV and (b) 20 GeV in two-dimensional plane of muon track eta and phi. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events in data 2018.
.png
(a): png pdf eps
.png
(b): png pdf eps
contact: Masato Aoki
The figures show the trigger plateau (offline muon pT > 25 GeV) efficiencies of level-1 single-muon triggers for a threshold of (a) 4 GeV and (b) 20 GeV in the endcap region, 1.05<|ημ|<2.4, as a function of instantaneous luminosity for different years in Run 2. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events. The efficiency of the L1 muon endcap trigger has been stable through Run 2. No strong dependence on the instantaneous luminosity was observed.
.png
(a): png pdf eps
.png
(b): png pdf eps
contact: Masato Aoki
The figures show the trigger plateau (offline muon pT > 25 GeV) efficiencies of level-1 single-muon triggers for a threshold of (a) 4 GeV and (b) 20 GeV in the endcap region, 1.05<|ημ|<2.4, as a function of the number of interactions per bunch crossing for different years in Run 2. The efficiency measurement was done using the Tag-and-Probe method in Z→μμ events. The efficiency of the L1 muon endcap trigger has been stable through Run 2. No strong dependence on the pile-up condition was observed.
.png
(a): png pdf eps
.png
(b): png pdf eps
contact: Masato Aoki
The figure shows the trigger plateau (offline muon pT > 25 GeV) efficiency for level-1 single muon triggers as a function of date in Run 2. The notation, L1_MU, is the name of level-1 single muon trigger menu at ATLAS, and the last digit corresponds to thresholds of transverse momentum in GeV for muons. The efficiency measurement was done using the Tag-and-Probe method in Z→μ&ny; events. The trigger requirements are tightened for higher pT threshold triggers in the endcap region, in addition to tighter pT threshold. L1_MU6 starts using three-station coincidence while L1_MU4 still uses two-station coincidence. L1_MU15 and L1_MU20 use additional coincidence with the TGC inner station. Additionally, events are rejected for small regions where the trigger rate is very high due to a poor magnetic field. The efficiency of the L1 muon endcap trigger has been stable through Run 2. .png
png pdf eps
contact: Masato Aoki
The figure shows the cross-sections of the level-1 single-muon triggers as a function of date in Run 2. The cross-section is defined to be the trigger rate divided by the instantaneous luminosity. The notation, L1_MU, is the name of level-1 single muon trigger at ATLAS, and the last digit corresponds to thresholds of transverse momentum in GeV for muons. The digit “11” means a special trigger condition w.r.t. “10” where the barrel muon trigger starts using three station coincidence instead of two. The digit “21” means a special trigger condition w.r.t. “20” where the barrel muon trigger starts disabling a part of triggers called the feet-trigger. For the endcap region, L1_MU6 starts using three-station coincidence while L1_MU4 still uses two-station coincidence. L1_MU15 and L1_MU20 use additional coincidence with the TGC inner station. Additionally, for L1_MU15 and L1_MU20, events are rejected for small regions where the trigger rate is very high due to a poor magnetic field. L1_MU4 was optimized during 2016 by requiring 3-station coincidence for the strip channels in the endcap region while earlier L1_MU4 still used 2-station strip coincidence, resulting in lower trigger rate while keeping the similar efficiency. L1_MU20 (and L1_MU21) was optimized at the beginning of 2017 by use of data-driven coincidence window in the endcap region, resulting in a lower trigger rate while keeping the same efficiency. .png
png pdf eps
contact: Masato Aoki
The figure shows the trigger rate for the level-1 three-muon trigger with a threshold of 4 GeV, L1_3MU4, as a function of instantaneous luminosity. The trigger coincidence window (CW) for the endcap region, 1.05<|ημ|<2.4, was optimized and it was deployed at the online ATLAS trigger system in 2018. In the figure, the trigger performance was compared between before and after the CW optimization. The rate for the trigger L1_3MU4 was reduced by about 7%. .png
png pdf eps
contact: Tomomi Kawaguchi, Masato Aoki
The figure shows the trigger rate for the level-1 three-muon trigger with a threshold of 6 GeV, L1_3MU6, as a function of instantaneous luminosity. The trigger coincidence window (CW) for the endcap region, 1.05<|ημ|<2.4, was optimized and it was deployed at the online ATLAS trigger system in 2018. In the figure, the trigger performance was compared between before and after the CW optimization. The rate for the trigger L1_3MU6 was reduced by about 7%. .png
png pdf eps
contact: Tomomi Kawaguchi, Masato Aoki
The figure shows the trigger rate for the level-1 four-muon trigger with a threshold of 4 GeV, L1_4MU4, as a function of instantaneous luminosity. The trigger coincidence window (CW) for the endcap level-1 muon trigger was optimized and it was deployed at the online ATLAS trigger system in 2018. In the figure, the trigger performance was compared between before and after the CW optimization. The rate for the trigger L1_4MU4 was reduced by about 8%. .png
png pdf eps
contact: Tomomi Kawaguchi, Masato Aoki
The figure shows the trigger rate for the level-1 three-muon trigger that requires three muons to satisfy three-muon trigger with a threshold of 4 GeV and also requires at least one of them to satisfy single-muon trigger with a threshold of 6 GeV, L1_MU6_3MU4, as a function of instantaneous luminosity. The trigger coincidence window (CW) for the endcap region, 1.05<|ημ|<2.4, was optimized and it was deployed at the online ATLAS trigger system in 2018. In the figure, the trigger performance was compared between before and after the CW optimization. The rate for the trigger L1_MU6_3MU4 was reduced by 6%. .png
png pdf eps
contact: Tomomi Kawaguchi, Masato Aoki
The figure shows the trigger rate for the level-1 two-muon trigger that requires two muons to satisfy two-muon trigger with a threshold of 6 GeV and also requires at least one of them to satisfy single-muon trigger with a threshold of 10 GeV, L1_MU11_2MU6, as a function of instantaneous luminosity. The convention “MU11” means a single-muon trigger with a threshold of 10 GeV with additional tight requirement (three-station coincidence) in the barrel region (|ημ|<1.05) with respect to the single-muon trigger with a threshold of 10 GeV with only two-station coincidence in the barrel region, MU10. The trigger coincidence window (CW) for the endcap region, 1.05<|ημ|<2.4, was optimized and it was deployed at the online ATLAS trigger system in 2018. In the figure, the trigger performance was compared between before and after the CW optimization. The rate for the trigger L1_MU11_2MU6 was reduced by 4%. .png
png pdf eps
contact: Tomomi Kawaguchi, Masato Aoki

2018 data

Level 1 muon barrel trigger performance in 2018: ATL-COM-DAQ-2018-181 (Dec 19, 2018)

The public results of the RPC detector performance is available at https://atlas.web.cern.ch/Atlas/GROUPS/PHYSICS/PLOTS/MUON-2018-09/index.html

Fraction of RPC high-pT trigger hits associated correctly to the collision Bunch Crossing (BC) for the whole RPC trigger system as a function of time.
Each point corresponds to a different pp collision run recorded by ATLAS in 2018 at √s = 13 TeV. Only runs without RPC problems and with integrated luminosity greater than L>50 pb-1 are used, altogether amounting to the integrated luminosity of L = 60.8 fb-1. The fraction is computed as the number of reconstructed muons with a Level 1 muon region of interest in the bunch crossing triggered by the Level 1 trigger over the number of reconstructed muons with a region of interest in the triggered bunch crossing and the previous and subsequent bunch crossings. Only statistical uncertainties are shown. Points that are below 99.6% have a lower fraction of trigger hits in the correct BC due to problems in the trigger hardware that led to a removal of part of the RPC readout (1 module out of 32 in total) from the data acquisition for a small period of time during these runs. This kind of timing misalignment is usually quickly recovered by a detector resynchronization and the fraction of hits in correct BC is therefore always above 99%.
.png
png pdf eps
contact: Marco Sessa & Zuzana Blenessy
Level 1 muon barrel trigger efficiency for offline muons with 0.1<|ημ|<1.05 as a function of their transverse momentum.
Only runs without RPC problems and with integrated luminosity greater than L>50 pb-1 are used, altogether amounting to the integrated luminosity of L = 60.8 fb-1. The efficiency is shown for six Level 1 trigger thresholds: MU4, MU6 and MU10 which require a coincidence of the two inner RPC stations, and MU11, MU20, MU21 with a further coincidence on the outer RPC stations. The MU20 threshold takes into account the full muon barrel region, while for the otherwise identical MU21 the feet trigger is excluded. For this reason, the trigger efficiency is higher for MU20. Efficiency is measured using a tag-and-probe method with Zμμ candidates, with no background subtraction applied. Muons with ημ<0.1 are excluded due to incomplete coverage with RPC detectors in this region. Only statistical uncertainties are shown.
.png
png pdf eps
contact: Marco Sessa & Zuzana Blenessy
Plateau value of the Level 1 muon barrel trigger efficiency for offline muons with pμT > 27 GeV and 0.1 < |ημ| < 1.05 as a function of time.
Each point corresponds to a different pp collision run recorded by ATLAS in 2018 at √s = 13 TeV. Only runs without RPC problems and with integrated luminosity greater than 50 pb-1 are used, altogether amounting to the integrated luminosity of L = 60.8 fb-1. The efficiency is shown for six Level 1 trigger thresholds: MU4, MU6 and MU10 which require a coincidence of the two inner RPC stations, and MU11, MU20, MU21 with a further coincidence on the outer RPC stations. The MU20 threshold takes into account the full muon barrel region, while for the otherwise identical MU21 the feet trigger is excluded. For this reason, the trigger efficiency is higher for MU20. Efficiency is measured using a tag-and-probe method with Zμμ candidates, with no background subtraction applied. Muons with ημ< 0.1 are excluded due to incomplete coverage with RPC detectors in this region. The plateau value is obtained by fitting the L1 muon barrel trigger efficiency curves as a function of offline muon pT above 27 GeV, for each run. Only statistical uncertainties are shown.
.png
png pdf eps
contact: Marco Sessa & Zuzana Blenessy
Level 1 muon barrel trigger efficiency for offline muons with pμT>25 GeV as a function of (a) η and (b) φ coordinates.
Only runs without RPC problems and with integrated luminosity greater than L>50 pb-1 are used, altogether amounting to the integrated luminosity of L = 60.8 fb-1. The efficiency is shown for two Level-1 thresholds: MU10 (low-pT) which requires a coincidence of the two inner RPC stations, and MU20 (high-pT) with a further coincidence on the outer RPC stations. Efficiency is measured using a tag-and-probe method with Zμμ candidates, with no background subtraction applied. Only statistical uncertainties are shown.
.png
(a) : png pdf eps
.png
(b) : png pdf eps
contact: Marco Sessa & Zuzana Blenessy

Performance plots of the Tile-Muon trigger: ATL-COM-DAQ-2018-165 (Nov 26, 2018)

The pseudo-rapidity distributions of the Level-1 RoIs (ηRoI) which fulfill the 20 GeV requirement (L1 MU20).

Figure 1: The L1 MU20 candidates are collected by a pass-through high-level trigger seeded by the L1_MU20 (HLT_noalg_L1MU20) in 2018 data with a center-of-mass energy of 13 TeV and a bunch-crossing interval of 25 ns. Runs with the TileCal coincidence running while not biasing the L1 trigger decisions are examined so that the rate reduction of L1_MU20 owing to the TileCal coincidence can be seen with respect to the recorded TileCal coincidence results in the offline analysis. A comparison between ηRoI of all the L1 MU20 entries (white histogram) and the subset which passes the TileCal coincidence requirement (blue histogram) shows the amount of the additional reduction at 1.05 < |ηRoI| < 1.3 by the TileCal coincidence.

The fraction of RoIs which are selected by the TileCal coincidence and match the offline combined muon which fulfill the ”medium” quality requirements is also shown without and with an offline pT requirement at 20 GeV for reference.

Figure 2: The L1 MU20 candidates are collected by a pass-through high-level trigger seeded by the L1_MU20 (HLT_noalg_L1MU20) in 2018 data with a center-of-mass energy of 13 TeV and a bunch-crossing interval of 25 ns. Runs with the TileCal coincidence running while not biasing the L1 trigger decisions are examined so that the rate reduction of L1_MU20 owing to the TileCal coincidence can be seen with respect to the recorded TileCal coincidence results in the offline analysis. A comparison between ηRoI of all the L1 MU20 entries (white histogram) and the subset which passes the TileCal coincidence requirement (blue histogram) shows the amount of the additional reduction at 1.05 < |ηRoI| < 1.3 by the TileCal coincidence.

The fraction of RoIs which are selected by the TileCal coincidence and match the offline combined muon which fulfill the ”medium” quality requirements is also shown with an offline pT requirement at 20 GeV for reference.

Figure 3: The L1 MU20 candidates are collected by a pass-through high-level trigger seeded by the L1_MU20 (HLT_noalg_L1MU20) in 2018 data with a center-of-mass energy of 13 TeV and a bunch-crossing interval of 25 ns. Runs with the TileCal coincidence running while not biasing the L1 trigger decisions are examined so that the rate reduction of L1_MU20 owing to the TileCal coincidence can be seen with respect to the recorded TileCal coincidence results in the offline analysis. A comparison between ηRoI of all the L1 MU20 entries (white histogram) and the subset which passes the TileCal coincidence requirement (blue histogram) shows the amount of the additional reduction at 1.05 < |ηRoI| < 1.3 by the TileCal coincidence.

.png
Figure 1: png pdf
.png
Figure 2: png pdf
.png
Figure 3: png pdf
contact: Masaya Ishino
The pseudo-rapidity distribution of the Level-1 RoIs (ηRoI) which fulfill the 20 GeV requirement (L1 MU20) after the deployment of the new TileCal coincidence in the Level-1 trigger decisions (White histogram). The L1 MU20 candidates are collected by a pass-through high-level trigger seeded by the L1_MU20 (HLT_noalg_L1MU20) in 2018 data with a center-of-mass energy of 13 TeV and a bunch-crossing interval of 25 ns. The η RoI distribution seen in runs before the deployment of the TileCal coincidence is also shown as a reference (blue triangle) to examine the reduction of the L1 MU20 trigger rate at 1.05 < |ηRoI| < 1.3, which is highlighted by the red rectangles. The reference histogram is normalized so that the entries out of the acceptance of the TileCal coincidence (1.05 < |ηRoI| < 1.3) are compatible between the two distributions for the comparison.

.png
png pdf
contact: Masaya Ishino
The trigger efficiency of the Level-1 MU20 RoI measured by the “tag-and-probe” method with Z→μμ candidates in 2018 data with a center-of-mass energy of 13 TeV and a bunch-crossing interval of 25 ns. The trigger efficiency is shown as a function of muon pT measured in the offline reconstruction. The trigger efficiency is compared between runs when TileCal coincidence is used in the Level-1 trigger decision (red) and is not used in the decision (blue). It is shown that the additional inefficiency due to the TileCal coincidence is limited up to ~2.5%, which is compatible with the expected inefficiency for muon tracks due to thin geometrical gaps between TileCal modules. .png
png pdf
contact: Masaya Ishino
The Level-1 rate for the single muon trigger with a pT threshold of 20 GeV as a function of instantaneous luminosity. The red (Blue) points correspond to data recorded with (without) TileCal coincidence requirement. This coincidence at 1.05 < |η| < 1.3 discards charged particles that only traverse the big wheel, which are originated from secondary interactions in the ATLAS Endcap toroid of the beam backgrounds. The comparison of the fit results shows that the reduction of the L1_MU20 trigger rate for all the muon spectrometer coverage is about 6% owing to the new TileCal coincidence requirement. .png
png pdf
contact: Masaya Ishino

2017 data

Performance plots for Level1 Barrel Muon Trigger: ATL-COM-DAQ-2018-008 (Feb 16, 2018)

L1_MU10 efficiency gain from new new feet trigger chambers in sector 12
Efficiency of Level 1 MU10 trigger in 2017 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of η at the interaction vertex of offline muon candidates in the barrel detector region, for a specific sector (corresponding to -2.16 < φ(mu at the interaction vertex) < -1.77) of the “feet” region of the ATLAS Muon Spectrometer. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass a “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU10 trigger requires that a candidate passed the 10 GeV threshold requirement of the Level 1 muon trigger system, using medium trigger chambers. The efficiency is measured on an inclusive sample selected using all non-muon Level 1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing. The plot shows the efficiency increase across the pseudo-rapidity range in the ATLAS Barrel Region, introduced by using the new trigger RPC chambers commissioned by the end of 2015 to cover the indicated φ range, corresponding to the detector support structure feet. The efficiency is also made more constant across η, instrumenting the positions where the detector structure support feet are placed.
ATL-COM-DAQ-2018-008-sector12_mu10.png
png pdf eps
L1_MU11 efficiency gain from new new feet trigger chambers in sector 12
Efficiency of Level 1 MU11 trigger in 2017 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of η at the interaction vertex of offline muon candidates in the barrel detector region, for a specific sector (corresponding to -2.16 < φ(mu at the interaction vertex) < -1.77) of the “feet” region of the ATLAS Muon Spectrometer. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass a “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU11 trigger requires that a candidate passed the 10 GeV threshold requirement of the Low-pT Level 1 muon trigger system, with a coincidence with a High-pT RPC chamber. The efficiency is measured on an inclusive sample selected using all non-muon Level 1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing. The plot shows the efficiency increase across the pseudo-rapidity range in the ATLAS Barrel Region, introduced by using the new trigger RPC chambers commissioned by the end of 2015 to cover the indicated φ range, corresponding to the detector support structure feet. The efficiency is also made more constant across η, instrumenting the positions where the detector structure support feet are placed.

png pdf eps
L1_MU10 efficiency gain from new new feet trigger chambers in sector 14
Efficiency of Level 1 MU10 trigger in 2017 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of η at the interaction vertex of offline muon candidates in the barrel detector region, for a specific sector (corresponding to -1.37 < φ(mu at the interaction vertex) < -0.98) of the “feet” region of the ATLAS Muon Spectrometer. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass a “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU10 trigger requires that a candidate passed the 10 GeV threshold requirement of the Level 1 muon trigger system, using medium trigger chambers. The efficiency is measured on an inclusive sample selected using all non-muon Level 1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing. The plot shows the efficiency increase across the pseudo-rapidity range in the ATLAS Barrel Region, introduced by using the new trigger RPC chambers commissioned by the end of 2015 to cover the indicated φ range, corresponding to the detector support structure feet. The efficiency is also made more constant across η, instrumenting the positions where the detector structure support feet are placed.

png pdf eps
L1_MU11 efficiency gain from new new feet trigger chambers in sector 14
Efficiency of Level 1 MU11 trigger in 2017 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of η at the interaction vertex of offline muon candidates in the barrel detector region, for a specific sector (corresponding to -1.37 < φ(mu at the interaction vertex) < -0.98) of the “feet” region of the ATLAS Muon Spectrometer. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass a “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU11 trigger requires that a candidate passed the 10 GeV threshold requirement of the Low-pT Level 1 muon trigger system, with a coincidence with a High-pT RPC chamber. The efficiency is measured on an inclusive sample selected using all non-muon Level 1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing. The plot shows the efficiency increase across the pseudo-rapidity range in the ATLAS Barrel Region, introduced by using the new trigger RPC chambers commissioned by the end of 2015 to cover the indicated φ range, corresponding to the detector support structure feet. The efficiency is also made more constant across η, instrumenting the positions where the detector structure support feet are placed.

png pdf eps
L1_MU10 efficiency in 2016 and 2017
Efficiency of Level 1 MU10 trigger in 2017 and comparison with 2016 trigger efficiency. The efficiency is plotted as a function of φ at the interaction vertex of offline muon candidates in the barrel detector region. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass a “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU10 trigger requires that a candidate passed the 10 GeV threshold requirement of the L1 muon trigger system, using medium trigger chambers. The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing.

png pdf eps
L1_MU11 efficiency in 2016 and 2017
Efficiency of Level 1 MU11 trigger in 2017 and comparison with 2016 trigger efficiency. The efficiency is plotted as a function of φ at the interaction vertex of offline muon candidates in the barrel detector region. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass a “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU11 trigger requires that a candidate passed the 10 GeV threshold requirement of the Low-pT L1 muon trigger system, with a coincidence with a High-pT RPC chamber. The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing.

png pdf eps
L1_MU10 efficiency 2017 / 2016 ratio
η-φ map of the ratio between the Level 1 Barrel muon trigger efficiency in 2017 and 2016 for the trigger threshold MU10. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass a “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU10 trigger requires that a candidate passed the 10 GeV threshold requirement of the L1 muon trigger system, using medium trigger chambers. The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing. The blank bins correspond to regions of the Muon Spectrometer not covered by RPC trigger detectors.

png pdf eps
L1_MU11 efficiency 2017 / 2016 ratio
η-φ map of the ratio between the Level 1 Barrel muon trigger efficiency in 2017 and 2016 for the trigger threshold MU11. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass a “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU11 trigger requires that a candidate passed the 10 GeV threshold requirement of the Low-pT Level 1 muon trigger system, with a coincidence with a High-pT RPC chamber. The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing. The blank bins correspond to regions of the Muon Spectrometer not covered by RPC trigger detectors.

png pdf eps
Turn-on curves for all L1 thresholds
Level 1 muon barrel trigger efficiency for reconstructed muons with pT > 15 GeV and |η| < 1.05 as a function of transverse momentum. The efficiency is shown for the six Level-1 thresholds: MU4, MU6, MU10 which require a coincidence of the two inner RPC stations, and MU11, MU20, MU21 with a further coincidence on the outer RPC stations. The MU20 threshold takes into account the full muon barrel region, while for the otherwise identical MU21 the new feet trigger is excluded. For this reason, the trigger efficiency is higher for MU20. The efficiency is measured using events selected by independent triggers and requiring an offline reconstructed muon.

png pdf eps
Plateau efficiencies for all L1 thresholds
Plateau value of the Level 1 muon barrel trigger efficiency (as a function of muon pT) for reconstructed muons with pT > 15 GeV and |η| < 1.05 as a function of time. Each point corresponds to a different ATLAS run recorded in 2017. Only runs with integrated luminosity greater than 50 pb-1 and at least 1000 reconstructed muons have been used. The efficiency is shown for the six Level-1 thresholds: MU4, MU6, MU10 which require a coincidence of the two inner RPC stations, and MU11, MU20, MU21 with a further coincidence on the outer RPC stations. The MU20 threshold takes into account the full muon barrel region, while for the otherwise identical MU21 the new feet trigger is excluded. For this reason, the trigger efficiency is higher for MU20. The efficiency is measured using events selected by independent triggers and requiring an offline reconstructed muon.

png pdf eps
BC Timing for each trigger tower
Fraction of the RPC High-pT trigger hits associated correctly to the collision Bunch Crossing for each Level 1 Barrel Muon trigger tower. The data is from a the pp runs at √s = 13 TeV with an integrated luminosity L=0.58 fb-1. The trigger sectors have a different number of towers: the small sectors have 6 trigger towers, the large sectors have 7 and the feet sectors have 8. The blank bin in sector 11 corresponds to a trigger tower masked in this specific run.

png pdf eps
BC timing fluctuations during 2017
Fraction of RPC High-pT trigger hits associated correctly to the collision Bunch Crossing for the whole RPC trigger system as a function of time. Each point corresponds to a different ATLAS run recorded in 2017. Only runs with integrated luminosity greater than 50 pb-1 have been used. In the period above day 100, corresponding to September-October 2017, two structures are observed, with the lower one with a BC fraction around 99.4%. This lower fraction with respect to the standard one of about 99.6% is due to some problems in the trigger hardware that led to a removal of part of the RPC readout (1 readout module out of 32 in total) from the data acquisition for a small period in those particular runs.

png pdf eps

Level-1 endcap muon trigger performance in 2016 and 2017: ATL-COM-DAQ-2017-112 (Sep 13, 2017)

Level-1 muon trigger efficiency at 2016 and 2017 for pT > 20 GeV (L1_MU20)
Efficiency of the L1_MU20 trigger for 2016 (black) and 2017 (red) are shown as a function of the offline muon transverse momentum. The L1_MU20 trigger requires that a candidate passed pT > 20 GeV threshold requirement of the L1 muon trigger system. The efficiency is estimated by tag-and-probe method using Z→μμ events. In 2017, look-up-table in the endcap region have been optimized using 2016 data.
.png
png pdf eps
Level-1 muon trigger rate at 2016 and 2017 for pT > 20 GeV (L1_MU20)
Trigger rate of the L1_MU20 trigger for 2016 (black) and 2017 (red) are shown as a function of the instantaneous luminosity. The L1_MU20 trigger requires that a candidate passed pT > 20 GeV threshold requirement of the L1 muon trigger system. In 2017, the overlap region at the barrel feet region and look-up table in the endcap region have been optimized using 2016 data.
.png
png pdf eps

Performance plots for Level1 Barrel Muon Trigger: ATL-COM-DAQ-2017-113 (Sep 13, 2017)

Efficiency of Level 1 (L1) MU10 trigger in 2017 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of η at the interaction vertex of offline muon candidates in the barrel detector region, for a specific sector (corresponding to -2.16 < φ(mu at the interaction vertex) < -1.77) of the “feet” region of the ATLAS Muon Spectrometer. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU10 trigger requires that a candidate passed the 10 GeV threshold requirement of the L1 muon trigger system, using middle trigger chambers. The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing. The plot shows the efficiency increase across the pseudo-rapidity range in the ATLAS Barrel Region, introduced by using the new trigger RPC chamber commissioned by the end of 2015 to cover the indicated φ range, corresponding to the detector support structure feet. The efficiency is also made more constant across η, instrumenting the positions where the detector structure support feet are placed. .png
png pdf eps
Efficiency of Level 1 (L1) MU11 trigger in 2017 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of η at the interaction vertex of offline muon candidates in the barrel detector region, for a specific sector (corresponding to -2.16 < φ(mu at the interaction vertex) < -1.77) of the “feet” region of the ATLAS Muon Spectrometer. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU11 trigger requires that a candidate passed the 10 GeV threshold requirement of the Low-pT L1 muon trigger system, with a coincidence with a High-pT RPC chamber. The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing. The plot shows the efficiency increase across the pseudo-rapidity range in the ATLAS Barrel Region, introduced by using the new trigger RPC chamber commissioned by the end of 2015 to cover the indicated φ range, corresponding to the detector support structure feet. The efficiency is also made more constant across η, instrumenting the positions where the detector structure support feet are placed. .png
png pdf eps
Efficiency of Level 1 (L1) MU10 trigger in 2017 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of η at the interaction vertex of offline muon candidates in the barrel detector region, for a specific sector (corresponding to -1.37 < φ(mu at the interaction vertex) < -0.98) of the “feet” region of the ATLAS Muon Spectrometer. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU10 trigger requires that a candidate passed the 10 GeV threshold requirement of the L1 muon trigger system, using middle trigger chambers. The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing. The plot shows the efficiency increase across the pseudo-rapidity range in the ATLAS Barrel Region, introduced by using the new trigger RPC chamber commissioned by the end of 2015 to cover the indicated φ range, corresponding to the detector support structure feet. The efficiency is also made more constant across η, instrumenting the positions where the detector structure support feet are placed. .png
png pdf eps
Efficiency of Level 1 (L1) MU11 trigger in 2017 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of η at the interaction vertex of offline muon candidates in the barrel detector region, for a specific sector (corresponding to -1.37 < φ(mu at the interaction vertex) < -0.98) of the “feet” region of the ATLAS Muon Spectrometer. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU11 trigger requires that a candidate passed the 10 GeV threshold requirement of the Low-pT L1 muon trigger system, with a coincidence with a High-pT RPC chamber. The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, in 13 TeV data from 2017 with 25 ns LHC bunch spacing. The plot shows the efficiency increase across the pseudo-rapidity range in the ATLAS Barrel Region, introduced by using the new trigger RPC chamber commissioned by the end of 2015 to cover the indicated φ range, corresponding to the detector support structure feet. The efficiency is also made more constant across η, instrumenting the positions where the detector structure support feet are placed. .png
png pdf eps
L1 muon barrel trigger efficiency for reconstructed muons with pT > 15 GeV and |η | < 1.05 as a function of transverse momentum. The efficiency is shown for the six Level-1 thresholds: MU4, MU6, MU10 which require a coincidence of the two inner RPC stations, and MU11, MU20, MU21 with a further coincidence on the outer RPC stations. MU21 threshold is equal to MU20 everywhere but in the “feet” region, where the new feet trigger does not have this threshold. The efficiency is measured using events selected by independent triggers. .png
png pdf eps

2016 data

Performance plots for Level1 Barrel Muon Trigger ATL-COM-DAQ-2017-035 (May 23, 2017)

Efficiency of Level 1 (L1) MU10 trigger in 2015 (blue triangles) and in 2016 (red dots) plotted as a function of φ at the interaction vertex of offline muon candidates in the barrel detector region. Z → µµ events from a fully-simulated ATLAS Monte Carlo are also overlaid as reference. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass “Medium” quality requirement and have a transverse momentum of at least 15 GeV and an absolute pseudo-rapidity lower than 1.05. The MU10 trigger requires that a candidate passed the 10 GeV threshold requirement of the L1 muon trigger system (using medium trigger chambers). The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, with no background subtraction applied, in 13 TeV data from 2015 and 2016 with 25 ns LHC bunch spacing. The statistical uncertainties are typically ~0.1%. The plot shows the general stability of the system with data taking and that in some areas the efficiency has increased thanks to fixing inefficient RPC chambers in the winter shutdown between 2015 and 2016. In particular, it shows the drastic efficiency increase (about 20% absolute) in the regions of the detector support structure feet, where new trigger RPC chambers were installed and commissioned by the end of 2015. The MC simulation was tuned with real RPC strip efficiencies measured on 2015 data and is overlaid to show the expectation of 2016 detector conditions. The MC efficiency of totally inefficient strips was set to 50% to be able to rescale if a given element should be repaired in the future. .png
png eps
Efficiency of Level 1 (L1) MU11 trigger in 2015 (blue triangles) and in 2016 (red dots) plotted as a function of φ at the interaction vertex of offline muon candidates in the barrel detector region. Z → µµ events from a fully-simulated ATLAS Monte Carlo are also overlaid as reference. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass “Medium” quality requirement and have a transverse momentum of at least 15 GeV and an absolute pseudo-rapidity lower than 1.05. The MU11 trigger requires that a candidate passed the 11 GeV threshold requirement of the L1 muon trigger system (using both medium and outer trigger chambers). The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, with no background subtraction applied, in 13 TeV data from 2015 and 2016 with 25 ns LHC bunch spacing. The statistical uncertainties are typically ~0.1%. The plot shows the general stability of the system with data taking and that in some areas the efficiency has increased thanks to fixing inefficient RPC chambers in the winter shutdown between 2015 and 2016. In particular, it shows the drastic efficiency increase (about 20% absolute) in the regions of the detector support structure feet, where new trigger RPC chambers were installed and commissioned by the end of 2015. The MC simulation was tuned with real RPC strip efficiencies measured on 2015 data and is overlaid to show the expectation of 2016 detector conditions. The MC efficiency of totally inefficient strips was set to 50% to be able to rescale if a given element should be repaired in the future. .png
png eps
Efficiency of Level 1 (L1) MU10 trigger in 2016 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of φ at the interaction vertex of offline muon candidates in the barrel detector region. It is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass “Medium” quality requirement and have a transverse momentum of at least 15 GeV and an absolute pseudo-rapidity lower than 1.05. The MU10 trigger requires that a candidate passed the 10 GeV threshold requirement of the L1 muon trigger system (using medium trigger chambers). The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, with no background subtraction applied, in 13 TeV data from 2016 with 25 ns LHC bunch spacing. The plot shows the drastic efficiency increase (about 20% absolute) introduced by using the new trigger RPC chambers installed and commissioned by the end of 2015 to cover the regions of the detector supporting structure feet. .png
png eps
Efficiency of Level 1 (L1) MU10 trigger in 2016 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of η at the interaction vertex of offline muon candidates in the barrel detector region, for a specific sector (corresponding to -1.96 < φ(mu at the interaction vertex) < -1.77) of the “feet” region of the ATLAS Muon Spectrometer. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU10 trigger requires that a candidate passed the 10 GeV threshold requirement of the L1 muon trigger system (using medium trigger chambers). The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, with no background subtraction applied, in 13 TeV data from 2016 with 25 ns LHC bunch spacing. The plot shows the efficiency increase across the pseudo-rapidity range in the ATLAS Barrel Region, introduced by using the new trigger RPC chambers installed and commissioned by the end of 2015 to cover the indicated φ range, corresponding to the detector support structure feet. The efficiency is also made more constant across η, instrumenting the positions where the detector structure support feet are placed. .png
png eps
Efficiency of Level 1 (L1) MU10 trigger in 2016 including (in green) or excluding (yellow) the newly commissioned trigger chambers in the “feet” region of the ATLAS Muon Spectrometer. The efficiency is plotted as a function of η at the interaction vertex of offline muon candidates in the barrel detector region, for a specific sector (corresponding to -1.17 < φ(mu at the interaction vertex) < -0.97) of the “feet” region of the ATLAS Muon Spectrometer. The efficiency is computed with respect to offline isolated muon candidates which are reconstructed using standard ATLAS software and are required to pass “Medium” quality requirement and have a transverse momentum of at least 15 GeV. The MU10 trigger requires that a candidate passed the 10 GeV threshold requirement of the L1 muon trigger system (using medium trigger chambers). The efficiency is measured on an inclusive sample selected using all non-muon L1 ATLAS triggers, with no background subtraction applied, in 13 TeV data from 2016 with 25 ns LHC bunch spacing. The plot shows the efficiency increase across the pseudo-rapidity range in the ATLAS Barrel Region, introduced by using the new trigger RPC chambers installed and commissioned by the end of 2015 to cover the indicated φ range, corresponding to the detector support structure feet. The efficiency is also made more constant across η, instrumenting the positions where the detector support structure feet are placed. .png
png eps

2015 data @ 13 TeV

Level 1 Barrel Muon trigger and RPC performance in 2015

RPC trigger coverage
Distribution RPC trigger hits in the pivot layer associated with an high-pT trigger, shown in terms of the η and φ strip coordinates. The black lines indicate the contours of individual RPC chambers. The data set corresponds to pp collisions collected with 25 ns spacing between colliding bunches.
.pdf
png pdf
RPC trigger coverage (in terms of strip index)
Distribution RPC trigger hits in the pivot layer associated with an high-pT trigger shown in term of the strip index of η and φ strips. The black lines indicate the contour of individual RPC chambers.
.pdf
png pdf
RPC efficiency
Distribution of the measured RPC "gap efficiency" of each gas volume, defined by the presence of hits on at least one of the two strip panels (η and φ), and of the "detector efficiency" for each strip panel, defined by the presence of hits in the strip panel. The total number of panels (η + φ) is 8592, the number of gaps is 4296. The efficiency is measured using standalone RPC tracks obtained removing the hits on the unit under test. Trigger biases are removed requiring that the remaining hits satisfy the trigger coincidence.
.pdf
png pdf
RPC dead strips
Distribution of the fraction of dead strips per readout panel for both views. Dead strips can originate from different reasons, e.g. readout problems, masking of noisy channels or gas gaps disconnected from HV. The peak at 1 shows that the fraction of readout panels in which all strips are dead is approximately 2%.
.pdf
png pdf
RPC cluster size
Distribution of RPC cluster size as measured in readout hits for the η and φ strips.
.pdf
png pdf
Average RPC cluster size per panel
Distribution of average RPC cluster size for each readout panel for both the η and φ views.
.pdf
png pdf
L1 Barrel Trigger Bunch Crossing identification
Difference between the event bunch crossing (BC) number identified by the Level-1 Muon Barrel trigger and the collision bunch crossing number, for muons passing reconstructed offline with pT > 15 GeV and passing the corresponding Level-1 threshold MU15. The collision bunch crossing is identified using independent triggers. The plot shows that 99.7% of the L1 barrel events have been tagged with the correct BC number. Data from a single pp collision run at √s = 13 TeV ( Oct 31/Nov 1, LHC fill 4560).
.pdf
png pdf
L1 Barrel Trigger timing
RPC hit time distribution for trigger hits, measured from readout data (yellow histogram), and its gaussian fit (blue line). The red dotted lines identify the collision Bunch Crossing (BC). One time unit on the horizontal axis is 1/8 of a BC (3.125 ns). The horizontal axis covers the readout window in which data are collected that corresponds to 8 BCs. The plot shows that the RPC trigger hit distribution is within the collision BC, and has a sigma equal to 0.94 ticks (= 2.9 ns).
.pdf
png pdf
L1 Barrel Trigger timing per tower
Fraction of RPC trigger hits associated correctly to the collision Bunch Crossing for each of the 428 Barrel Muon trigger towers. The red contours show the new trigger towers of the “feet”-chamber upgrade that have been activated at the end of 2015 data taking and have not been yet fully commissioned. One tower with hardware problems (Tower=2, Sector=38) is visible as an orange area. The two white areas (Tower=3, Sector=23, 24, 55, 56) correspond to the “elevator” chambers, not yet commissioned in 2015. Data from pp runs at √s = 5 TeV, integrated luminosity L=28 pb-1.
.pdf
png pdf
L1 Barrel Trigger efficiency as a function of η
L1 muon barrel trigger efficiency for reconstructed muons with pT>15 GeV as a function of η. The efficiency is shown for two thresholds: MU10 (pT > 10 GeV, selected with a coincidence of the two inner RPC stations) and MU11 (pT > 10 GeV selected with a further coincidence with the outer RPC stations). The dashed histograms show the results from a special MC simulation which includes measured efficiencies of the RPC chambers. The plot shows a lower trigger efficiency in regions where the detector coverage is lower due to the barrel toroid mechanical structures. The efficiency was measured using events selected by independent triggers.
.pdf
png pdf
L1 Barrel Trigger efficiency as a function of φ
L1 muon barrel trigger efficiency for reconstructed muons with pT > 15 GeV as a function of φ. The efficiency is shown for two thresholds: MU10 (pT > 10 GeV, selected with a coincidence of the two inner RPC stations) and MU11 (pT > 10 GeV selected with a further coincidence with the outer RPC stations). The dashed histograms show the results from a special MC simulation which includes measured efficiencies of the RPC chambers. The regions with lower efficiency around φ = -2 and φ = -1 correspond to the “feet” structures that support the ATLAS calorimeters, in which the muon chamber coverage is reduced. The efficiency was measured using events selected by independent triggers.
.pdf
png pdf
L1 Barrel Trigger efficiency as a function of pT
L1 muon barrel trigger efficiency for reconstructed muons with pT > 15 GeV and |η| < 1.05 as a function of transverse momentum. The efficiency is shown for the six Level-1 thresholds: MU4,MU6, MU10 which require a coincidence of the two inner RPC stations, and MU11,MU15,MU20 with a further coincidence on the outer RPC stations. The fitted plateau efficiency for MU10 and MU11 is also shown. The efficiency was measured using events selected by independent triggers.
.pdf
png pdf
RPC efficiency with the Z “tag and probe” method
The plot shows the distribution of the measured RPC detector efficiencies defined by the positive response of the η strips (similar to Figure 3) measured using reconstructed muons from Z → μ μ decays with the “tag-and-probe method”.
.pdf
png pdf

Performance of Level1 Endcap FI coincidence in Run2:

(top) Efficiency of Level1(L1) muon trigger with the pT threshold of 15 GeV (L1_MU15) in the region 1.3 < |η| <1.9, as a function of φ. It is computed with respect to offline muon candidates which are reconstructed using standardATLAS software and are categorized as “combined” muons with tracks in InnerDetector and MuonSpectrometer. It is measured in the Tag-and-Probe method using the Z→μμ candidate events in runs of 13 TeV data taking with 25ns LHC bunch spacing, applying 15 GeV threshold to the offline muons used as probe. Blue and red points show the efficiency [without] and [with] the FI coincidence enabled, respectively. The values “with FI coincidence” are calculated with requiring coincidence flags in the FI chambers. (bottom) Ratio of the efficiency values in the top plot: [with FI] / [without FI]. The values ( ~98% ) shows the efficiency in the same pseudo-rapidity region 1.3 < |η| < 1.9 as in the top plot, which is negligible in the total eta region. .pdf
png pdf
contact: Toshi Sumida
(top) Efficiency of L1_MU15 trigger in the endcap region, as a function of pT of offline muons. It is measured in the Tag-and-Prove method using Z→μμ events. Blue and red points show the efficiency without and with the FI coincidence enabled, respectively. (bottom) Ratio of the absolute trigger efficiency values in the top plot: [with FI] / [without FI], which shows the additional efficiency of the FI coincidence. .pdf
png pdf
contact: Toshi Sumida
(top) η distributions of Region of Interest (RoI) from the L1_MU15 trigger. The number of the entries are normalized with the integrated luminosities in the runs with and without the FI coincidence enabled. (bottom) Reduction on the trigger rate of L1_MU15, calculated in (1-N[with FI]/N[without FI], N: number of entry in each bin). The rate reductions in the regions with no FI chambers are consistent with 0 within the errors, which are computed in the statistics only. The binning for those regions are merged to reduce the visual effect from the statistical fluctuation. .pdf
png pdf
contact: Toshi Sumida
(top) η distributions of Region of Interest (RoI) from the L1 muon trigger with the pT threshold of 20 GeV (L1_MU20). The number of the entries are normalized with the integrated luminosities in the runs with and without the FI coincidence enabled. (bottom) Reduction on the trigger rate of L1_MU20, calculated in (1-N[with FI]/N[without FI], N: number of entry in each bin). The rate reductions in the regions with no FI chambers are consistent with 0 in the errors, which are computed in the statistics only. The binning for those regions are merged to reduce the visual effect from the statistical fluctuation. .pdf
png pdf
contact: Toshi Sumida
Trigger rates of the L1_MU15 in the runs with and without the FI coincidence enabled, as functions of the instantaneous luminosity of LHC. The reduction computed from the slope of the linear fitting is 15%. .pdf
png pdf
contact: Toshi Sumida
Trigger rates of the L1_MU20 in the runs with and without the FI coincidence enabled, as functions of the instantaneous luminosity of LHC. The reduction computed from the slope of the linear fitting is 21%. .pdf
png pdf
contact: Toshi Sumida

Trigger rates for muon trigger for Run2: (September 23, 2015)

The Level 1 rate for the single muon trigger with a pT threshold of 20 GeV versus instantaneous luminosity. The black (red) points correspond to data recorded with (without) a coincidence between the FI (Forward-Inner) muon layers with the big-wheel of the muon spectrometer. This coincidence removes collision background from secondary interactions in the ATLAS Endcap toroid which produces particles that only traverse the big wheel. These background signals arrive at the big-wheel layer with a delay of approximately 25ns and therefore did not contribute significantly to the muon trigger rate during the 50ns running in Run-1 and Run-2. The rate reduction due the coincidence is approximately 25%.

.pdf
png pdf
contact: Philipp Fleischmann

L1Muon Trigger : 2011-2012

The expected eta-distributions of the LVL1 muon trigger in Run-2: ATL-COM-DAQ-2015-205 (Dec. 2016)

The pseudo-rapidity (η) distributions of the Level-1 muon trigger objects (MU20) as expected in Run 2 are shown (an update of the Fig.43 of the ATLAS TDAQ Phase-1 TDR [1]). They are emulated by using data taken in 2012 at a centerof-mass energy of 8 TeV and a bunch-crossing interval of 25 ns.

The black line shows the η distribution of MU20 in Run 1. The emulated rejection with new Level-1 muon trigger logics of FI-TGC coincidence [1], Tile Calorimeter coincidence [1], and hot RoI mask are shown in white, hatched green, and hatched magenta respectively. The hot RoI masking is applied to small specific regions where a particularly high rate is observed due to a weak magnetic field.

The red histogram shows the η distribution of MU20 that are associated with an offline reconstructed muon. The green histogram shows the η distribution of MU20 that are associated with an offline reconstructed muon with a transverse momentum of more than 20 GeV.

[1] CERN-LHCC-2013-018 (2013), ATLAS Collaboration, Technical Design Report for the Phase-I Upgrade of the ATLAS TDAQ System

.png
png pdf

contact: Masaya Ishino
.png
png pdf

contact: Masaya Ishino
The pseudo-rapidity (η) distributions of the Level-1 muon trigger objects (MU20) as expected in Run 2 are shown (an update of the Fig.43 of the ATLAS TDAQ Phase-1 TDR [1]). They are emulated by using data taken in 2012 at a centerof-mass energy of 8 TeV and a bunch-crossing interval of 25 ns.

The black line shows the η distribution of MU20 in Run 1. The emulated rejection with new Level-1 muon trigger logics of FI-TGC coincidence [1], Tile Calorimeter coincidence [1], and hot RoI mask are shown in white, hatched green, and hatched magenta respectively. The hot RoI masking is applied to small specific regions where a particularly high rate is observed due to a weak magnetic field.

The green histogram shows the η distribution of MU20 that are associated with an offline reconstructed muon with a transverse momentum of more than 20 GeV.

[1] CERN-LHCC-2013-018 (2013), ATLAS Collaboration, Technical Design Report for the Phase-I Upgrade of the ATLAS TDAQ System

.png
png pdf

contact: Masaya Ishino
.png
png pdf

contact: Masaya Ishino
The pseudo-rapidity (η) distributions of the Level-1 muon trigger objects (MU20) as expected in Run 2 are shown (an update of the Fig.43 of the ATLAS TDAQ Phase-1 TDR [1]). They are emulated by using data taken in 2012 at a centerof-mass energy of 8 TeV and a bunch-crossing interval of 25 ns.

The black line shows the η distribution of MU20 in Run 1. The emulated rejection with new Level-1 muon trigger logics of FI-TGC coincidence [1], Tile Calorimeter coincidence [1], and hot RoI mask are shown in white, hatched green, and hatched magenta respectively. The hot RoI masking is applied to small specific regions where a particularly high rate is observed due to a weak magnetic field.

The red histogram shows the η distribution of MU20 that are associated with an offline reconstructed muon.

[1] CERN-LHCC-2013-018 (2013), ATLAS Collaboration, Technical Design Report for the Phase-I Upgrade of the ATLAS TDAQ System

.png
png pdf

contact: Masaya Ishino
The pseudo-rapidity (η) distributions of the Level-1 muon trigger objects (MU20) as expected in Run 2 are shown (an update of the Fig.43 of the ATLAS TDAQ Phase-1 TDR [1]). They are emulated by using data taken in 2012 at a centerof-mass energy of 8 TeV and a bunch-crossing interval of 25 ns.

The black line shows the η distribution of MU20 in Run 1. The emulated rejection with new Level-1 muon trigger logics of FI-TGC coincidence [1], Tile Calorimeter coincidence [1], and hot RoI mask are shown in white, hatched green, and hatched magenta respectively. The hot RoI masking is applied to small specific regions where a particularly high rate is observed due to a weak magnetic field.

[1] CERN-LHCC-2013-018 (2013), ATLAS Collaboration, Technical Design Report for the Phase-I Upgrade of the ATLAS TDAQ System

.png
png pdf

contact: Masaya Ishino

Performance of the ATLAS Level-1 Trigger: ATL-COM-DAQ-2012-033 (May 02, 2012)

η distribution of Level-1 Regions of Interest (RoIs) passing the L1_MU10 trigger, measured in a run from 2011 and a run from 2012. Distributions are individually normalized to unit area. The large fraction at approximately η=1 is due to gamma rays from the beam penetrating through a narrow unshielded region between the barrel and endcap regions of the experiment. Additional shielding was installed in this region between 2011 and 2012 running. L1_MU10 is a trigger for a single muon with transverse momentum above 10GeV, requiring a coincidence of hits across three-stations in the TGC and two-stations in the RPC regions of the L1Muon trigger chambers. .png
png eps
contact: Will Buttinger
η distribution of Level-1 Regions of Interest (RoIs) passing the L1_MU11 trigger, with the distribution of the subset of RoIs matched (ΔR<0.2) to an offline reconstructed muon (with a combined inner detector and muon spectrometer track and additional interaction-point parameter cuts to exclude cosmic muons, and pT at least 3 GeV), and offline reconstructed muons with a pT greater than 10 GeV. L1_MU11 is a trigger for a single muon with transverse momentum above 10GeV, requiring a coincidence of hits across three-stations in all regions of the L1Muon trigger chambers. .png
png eps
contact: Will Buttinger

L1 Barrel Muon Trigger Efficiency 2012

L1 Barrel Muon Trigger Efficiency with 2012 Data: ATL-COM-DAQ-2014-007 (February 21, 2014)

L1 muon barrel trigger efficiency vs. ϕ
Offline data quality monitoring - LHC fill 3203, 20-21 October 2012.
L1 muon barrel trigger efficiency for the low-pT MU10 threshold (muons with pT > 10 GeV selected with a coincidence of the two inner RPC stations) and the high-pT MU11 threshold (muons with pT > 10 GeV selected with a further coincidence the third outer RPC stations), as a function of ϕ, and its comparison with MC data.
The plot shows a lower trigger efficiency in the feet region (around ϕ = -1 and ϕ = -2) where the detector coverage is lower due to the ATLAS mechanical supports. The trigger efficiency is also lower in the small sectors than in the large ones, because of the toroid mechanical structures again affecting the detector coverage.
The efficiency is measured with offline reconstructed combined muons of pT > 15 GeV and an independent triggers based on jets and missing transverse energy.
.png
png pdf
contact: Massimo Corradi, Riccardo Vari
L1 muon barrel trigger efficiency vs. η
Offline data quality monitoring - LHC fill 3203, 20-21 October 2012.
L1 muon barrel trigger efficiency for the low-pT MU10 threshold (muons with pT > 10 GeV selected with a coincidence of the two inner RPC stations) and the high-pT MU11 threshold (muons with pT > 10 GeV selected with a further coincidence the third outer RPC stations), as a function of η, and its comparison with MC data.
The plot shows a lower trigger efficiency in regions where the detector coverage is lower due to the barrel toroid mechanical structures.
The efficiency is measured with offline reconstructed combined muons of pT > 15 GeV and an independent trigger based on jets and missing transverse energy.
.png
png pdf
contact: Massimo Corradi, Riccardo Vari
L1 muon trigger efficiency vs. η
Offline data quality monitoring - LHC fill 3203, 20-21 October 2012.
L1 muon trigger efficiency for the barrel (1.05 < η < 1.05, within the red dotted lines) and end-cap regions, as a function of η, and its comparison to MC data. The barrel low-pT MU10 threshold selects muons with pT > 10 GeV with a coincidence of the two inner RPC stations, while the high-pT MU11 threshold selects muons with pT > 10 GeV with a further coincidence the third outer RPC station. The end-cap MU10 and MU11 thresholds select muons with pT > 10 GeV with a coincidence of three TGC stations.
The plot shows a lower trigger efficiency than the end-cap in some barrel regions, because of the reduced RPC detector coverage where the barrel toroid mechanical structures and the ATLAS feet supports are.
The efficiency is measured with offline reconstructed combined muons of pT > 15 GeV and an independent trigger based on jets and missing transverse energy.
.png
png pdf
contact: Massimo Corradi, Riccardo Vari
L1 muon barrel trigger turn on curves
Offline data quality monitoring - LHC fill 3203, 20-21 October 2012.
L1 muon barrel trigger efficiency as a function of pT, for the six trigger thresholds.
MU4, MU6, MU10 are the low-pT thresholds (muons selected with the two inner RPC stations), while MU11, MU15, MU20 are the high-pT thresholds (low-pT muons confirmed with the third outer RPC station).
The lower trigger efficiency for the three high-pT thresholds is due to the reduced RPC detector coverage in the outer planes, due to the ATLAS feet support structure.
The efficiency is measured with offline reconstructed combined muons and an independent trigger based on jets and missing transverse energy.
.png
png pdf
contact: Massimo Corradi, Riccardo Vari
L1 muon barrel trigger efficiency (ϕ vs. η)
Offline data quality monitoring - LHC fill 3203, 20-21 October 2012.
L1 muon barrel trigger efficiency for the high-pT MU11 threshold (muons with pT > 10 GeV selected with a coincidence of three RPC stations), as a function of η and ϕ.
Orange and red regions represent lower trigger efficiency, due to the reduced RPC detector geometrical acceptance in the regions where there are toroid mechanical supports. The regions where there are no RPC detectors at all are marked as white.
The efficiency is measured with offline reconstructed combined muons of pT > 10 GeV and an independent trigger based on jets and missing transverse energy.
.png
png pdf
contact: Massimo Corradi, Riccardo Vari
L1 muon trigger efficiency (ϕ vs. η)
Offline data quality monitoring - LHC fill 3203, 20-21 October 2012.
L1 muon barrel and end-cap trigger efficiency for the high-pT MU11 threshold (muons with pT > 10 GeV selected with a coincidence of three RPC stations in the barrel region, and three TGC stations in the end-cap region), as a function of eta and phi.
Orange and red regions represent lower trigger efficiency, due to the reduced RPC detector geometrical acceptance in the regions where there are toroid mechanical supports. The regions where there are no RPC detectors at all are marked as white.
The efficiency is measured with offline reconstructed combined muons of pT > 10 GeV and an independent trigger based on jets and missing transverse energy.
.png
png pdf
contact: Massimo Corradi, Riccardo Vari
L1 muon barrel trigger Bunch Crossing identification
Offline data quality monitoring - LHC fill 3203, 20-21 October 2012.
L1 muon barrel trigger Bunch Crossing number distribution for the high-pT MU11 threshold (muons with pT > 10 GeV selected with a coincidence of three RPC stations).
The plot shows that 99.64% of the L1 barrel events have been tagged with the correct Bunch Crossing number.
Events have been selected with all L1 muon triggers and reconstructed offline muons.
.png
png pdf
contact: Massimo Corradi, Riccardo Vari
L1 muon barrel readout Bunch Crossing identification
Offline data quality monitoring - LHC fill 3203, 20-21 October 2012.
RPC timing distribution for trigger hits measured from readout data as a function of time (yellow histogram), and its gaussian fit (blue line). The red dotted lines identify the collision Bunch Crossing.
One time unit on the X-axis is 1/8 of a BC (3.125 ns).
The plot shows that the RPC barrel hit distribution is within the collision Bunch Crossing, and has a sigma equal to 0.9 ticks (= 2.83 ns).
Events have been selected with all L1 muon triggers and reconstructed offline muons.
.png
png pdf
contact: Massimo Corradi, Riccardo Vari

Performance Estimation for Phase-II Level-0/1 Muon Trigger: ATL-COM-DAQ-2014-010 (March 07, 2014)

Distributions of the Run 1 Level-1 muon candidates matched with the tracks reconstructed by a full offline analysis as a function of the inverse of the offline transverse momentum 1/pT and the magnitude of the polar-angle difference |β| of the segments measured by the precision tracking chambers between the outer (middle) and middle (inner) stations in the barrel (endcap). This is the study of the expected Phase-II upgrade performance of a cut on |β| made with a Level-0/1 MDT based muon trigger. The study is based on a data sample for the LHC fills of 3440-3442 and 3447-3453 taken on 15-16 Dec. 2012 with a center-of-mass energy of 8 TeV and a bunch-crossing interval of 25 nsec. The events are selected by requiring the Level-1 muon trigger with transverse momentum threshold of 20 GeV. The candidates are selected by the requirements expected for the Phase-I upgrade, based on the precision tracking chambers in the inner station of the endcap and the extended-barrel tile calorimeter, and a spot mask proposed for the Phase-I or Phase-II upgrade, in the transition region of the barrel and endcap toroidal magnets. .png
png eps
.png
png eps
contact: Yasuyuki Horii
Distribution of the Run 1 Level-1 muon candidate's transverse momentum pT for muons matched with the tracks reconstructed by a full offline analysis with various trigger requirements, including the proposed use of the MDT chambers for the Phase-II upgrade. The study is based on a data sample for the LHC fills of 3440-3442 and 3447-3453 taken on 15-16 Dec. 2012 with a center-of-mass energy of 8 TeV and a bunch-crossing interval of 25 nsec. Events are selected by requiring the Level-1 muon trigger with transverse momentum threshold of 20 GeV. The white (unshaded) distribution is obtained by applying the requirements expected for the Phase-I upgrade, based on the precision tracking chambers in the inner station of the endcap (SW) and the extended-barrel tile calorimeter. The red (parallel-hatched) distribution is obtained by further applying a spot mask in the transition region of the barrel and endcap toroidal magnets proposed for the Phase-I or Phase-II upgrade. The blue (cross-hatched) distribution is obtained by further applying a requirement based on the MDT chambers proposed for the Phase-II upgrade. The distributions are overlaid. .png
png eps
contact: Yasuyuki Horii
The efficiency of selecting the muon candidates matched with the tracks reconstructed by a full offline analysis for a spot mask in the transition region of the barrel and endcap toroidal magnets proposed for the Phase-I or Phase-II upgrade (red dots with error bars) and for a requirement based on the MDT chambers proposed for the Phase-II upgrade (blue open circles with error bars) depending on the offline transverse momentum pT. The study is based on a data sample for the LHC fills of 3440-3442 and 3447-3453 taken on 15-16 Dec. 2012 with a center-of-mass energy of 8 TeV and a bunch-crossing interval of 25 nsec. Events are selected by requiring the Level-1 muon trigger with transverse momentum threshold of 20 GeV. The values are relative to an expected condition after the requirements expected for the Phase-I upgrade, based on the precision tracking chambers in the inner station of the endcap and the extended-barrel tile calorimeter. .png
png eps
contact: Yasuyuki Horii
Distribution of the Run 1 Level-1 muon candidate's pseudorapidity ηL1 for muons matched with the tracks reconstructed by a full offline analysis with various trigger requirements, including the proposed use of the MDT chambers for the Phase-II upgrade. The study is based on a data sample for the LHC fills of 3440-3442 and 3447-3453 taken on 15-16 Dec. 2012 with a center-of-mass energy of 8 TeV and a bunch-crossing interval of 25 nsec. Events are selected by requiring the Level-1 muon trigger with transverse momentum threshold of 20 GeV. The white (unshaded) distribution is obtained by applying the requirements expected for the Phase-I upgrade, based on the precision tracking chambers in the inner station of the endcap (SW) and the extended-barrel tile calorimeter. The red (parallel-hatched) distribution is obtained by further applying a spot mask in the transition region of the barrel and endcap toroidal magnets proposed for the Phase-I or Phase-II upgrade. The blue (cross-hatched) distribution is obtained by further applying a requirement based on the MDT chambers proposed for the Phase-II upgrade. The green (shaded) distribution is obtained by further applying a requirement on the transverse momentum pT reconstructed in a full offline analysis to satisfy pT > 20 GeV. The distributions are overlaid. .png
png eps
contact: Yasuyuki Horii


2010 data @ 7 TeV

RPC timing

L1 RPC trigger timing

Distribution of the trigger time difference of the L1 RPC trigger in units of bunch crossings (BC) with respect to the minimum bias L1 trigger for collision events containing an offline muon with | eta | <1.05, reconstructed using the muon spectrometer and inner detector data. The L1 RoI to offline matching criteria is DR<0.5. The timing window has been temporarily stretched to accept muon triggers in BC={-2,-1,0} to ensure sufficient statistics for the timing calibration with data. Shown is the calibration obtained with cosmic radiation (black) and the first calibration obtained with collision data (red).


jpg pdf
L1 RPC low-pt trigger timing
Bunch-Crossing (BC) distribution of the RPC low-pt trigger, from any trigger sector, with respect to the L1A BC trigger before and after a calibration with pp data. The blue dotted line represent the BC distribution obtained after calibration with cosmic data.

png eps
L1 RPC high-pt trigger timing
Bunch-Crossing (BC) distribution of the RPC high-pt trigger, from any trigger sector, with respect to the RPC low-pt trigger before and after calibration with pp data.

png eps

TGC phase scan

TGC Clock Phase Scan
The plot shows the fraction of the TGC hits in the bunch crossing before the colliding bunch as a function of the clock phase shift of the TGC, from which the optimal delay time for the opening gate can be determined. The numerator is the TGC hits in BC={-1}, the denominator is the sum of the TGC hits in BC={-1,0,1} relative to the colliding bunch. A transverse momentum of offline combined muon of greater 5 GeV/c is required. The optimal timing is between -1 nsec and -2 nsec. An adjustment in the TGC timing of -4 nsec is chosen to have a sufficient margin to cover the fluctuation of fiber length between LHC and ATLAS by the variation in temperature.

jpg pdf

RPC and TGC rates

Result of a clock fine delay scan between the Muon-to-CTP-Interface (MUCTPI) and the sector logic modules of the muon trigger detectors (RPC and TGC).

The test indirectly measures the relative phase between the incoming muon trigger sector data and the MUCTPI clock. This phase relationship needs to be known in order to safely strobe the incoming data without any errors. The result shows that with the current operating point (MUCTPI clock fine delay setting of 3ns), the signals are strobed correctly with no errors and with timing margins of more than +/- 5ns for all 208 sectors.

Test procedure: the phase of the MUCTPI clock that strobes the incoming muon sector data is shifted by 0.5ns steps over the full 25ns range, while the sector logic modules are sending a known repetitive test pattern. For each delay step, the data transmission is checked using diagnostics memories. The number of sectors with at least one error is shown in the histogram per delay setting. These delay settings with transmission errors, which need to be avoided, cluster far away from the current operating point (delay setting of 3ns) with margins of more than +/- 5ns.

png png
Rate of each of the RPC (centre lines) and TGC (left and right disks) sectors.
Taken during a run of stable beams, the eight-fold structure of the muon detector can be seen in the RPC, this is harder to see in the TGC due to limited statistics. The numbers on the blue/purple coloured background show the MIOCT slot numbers, showing how these are linked between TGC and RPC.

png
RPC and TGC rates as a function of transverse momentum threshold
Shows the rate as a function of PT threshold (y-axis) for each sector (x-axis). The first 4 sectors correspond to the RPC, any gaps appear due to limited statistics. Each threshold can have 2 candidates and there is also a total. The remaining sectors are for the TGC, where the 4th trigger threshold was not being used. Each plot is one MIOCT board (its slot number gives the position of the detector inputs, as shown in the above plot) and all inputs report similar rates.

png


Major updates:
-- JoergStelzer - 13-Jun-2011 Responsible: JoergStelzer
Subject: public

Topic attachments
I Attachment History Action Size Date Who Comment
PDFpdf ATL-COM-DAQ-2014-007-fig1.pdf r1 manage 112.5 K 2014-02-21 - 20:07 RiccardoVari  
PNGpng ATL-COM-DAQ-2014-007-fig1.png r1 manage 834.0 K 2014-02-21 - 20:17 RiccardoVari  
PDFpdf ATL-COM-DAQ-2014-007-fig2.pdf r1 manage 116.0 K 2014-02-21 - 20:22 RiccardoVari  
PNGpng ATL-COM-DAQ-2014-007-fig2.png r1 manage 840.2 K 2014-02-21 - 20:24 RiccardoVari  
PDFpdf ATL-COM-DAQ-2014-007-fig3.pdf r1 manage 120.1 K 2014-02-21 - 20:24 RiccardoVari  
PNGpng ATL-COM-DAQ-2014-007-fig3.png r1 manage 868.1 K 2014-02-21 - 20:24 RiccardoVari  
PDFpdf ATL-COM-DAQ-2014-007-fig4.pdf r1 manage 57.4 K 2014-02-21 - 20:24 RiccardoVari  
PNGpng ATL-COM-DAQ-2014-007-fig4.png r1 manage 209.9 K 2014-02-21 - 20:24 RiccardoVari  
PDFpdf ATL-COM-DAQ-2014-007-fig5.pdf r1 manage 75.2 K 2014-02-21 - 20:24 RiccardoVari  
PNGpng ATL-COM-DAQ-2014-007-fig5.png r1 manage 157.0 K 2014-02-21 - 20:24 RiccardoVari  
PDFpdf ATL-COM-DAQ-2014-007-fig6.pdf r1 manage 90.5 K 2014-02-21 - 20:24 RiccardoVari  
PNGpng ATL-COM-DAQ-2014-007-fig6.png r1 manage 200.8 K 2014-02-21 - 20:24 RiccardoVari  
PDFpdf ATL-COM-DAQ-2014-007-fig7.pdf r1 manage 57.0 K 2014-02-21 - 20:24 RiccardoVari  
PNGpng ATL-COM-DAQ-2014-007-fig7.png r1 manage 130.5 K 2014-02-21 - 20:26 RiccardoVari  
PDFpdf ATL-COM-DAQ-2014-007-fig8.pdf r1 manage 73.7 K 2014-02-21 - 20:26 RiccardoVari  
PNGpng ATL-COM-DAQ-2014-007-fig8.png r1 manage 143.9 K 2014-02-21 - 20:26 RiccardoVari  
Unknown file formateps ATL-COM-DAQ-2014-010-fig1a.eps r1 manage 38.0 K 2014-03-07 - 15:20 YasuyukiHorii  
PNGpng ATL-COM-DAQ-2014-010-fig1a.png r1 manage 25.1 K 2014-03-07 - 15:20 YasuyukiHorii  
Unknown file formateps ATL-COM-DAQ-2014-010-fig1b.eps r1 manage 45.1 K 2014-03-07 - 15:20 YasuyukiHorii  
PNGpng ATL-COM-DAQ-2014-010-fig1b.png r1 manage 25.6 K 2014-03-07 - 15:20 YasuyukiHorii  
Unknown file formateps ATL-COM-DAQ-2014-010-fig2.eps r1 manage 17.1 K 2014-03-07 - 15:20 YasuyukiHorii  
PNGpng ATL-COM-DAQ-2014-010-fig2.png r1 manage 36.5 K 2014-03-07 - 15:20 YasuyukiHorii  
Unknown file formateps ATL-COM-DAQ-2014-010-fig3.eps r1 manage 10.1 K 2014-03-07 - 15:20 YasuyukiHorii  
PNGpng ATL-COM-DAQ-2014-010-fig3.png r1 manage 19.2 K 2014-03-07 - 15:20 YasuyukiHorii  
Unknown file formateps ATL-COM-DAQ-2014-010-fig4.eps r1 manage 24.4 K 2014-03-07 - 15:20 YasuyukiHorii  
PNGpng ATL-COM-DAQ-2014-010-fig4.png r1 manage 28.0 K 2014-03-07 - 15:20 YasuyukiHorii  
Unknown file formateps ATL-COM-DAQ-2015-142-fig1a.eps r1 manage 27.4 K 2015-09-20 - 04:20 TomoeKishimoto  
PNGpng ATL-COM-DAQ-2015-142-fig1a.png r1 manage 21.4 K 2015-09-20 - 04:20 TomoeKishimoto  
Unknown file formateps ATL-COM-DAQ-2015-142-fig1b.eps r1 manage 25.9 K 2015-09-20 - 04:20 TomoeKishimoto  
PNGpng ATL-COM-DAQ-2015-142-fig1b.png r1 manage 21.5 K 2015-09-20 - 04:20 TomoeKishimoto  
Unknown file formateps ATL-COM-DAQ-2015-142-fig2.eps r1 manage 10.9 K 2015-09-20 - 04:20 TomoeKishimoto  
PNGpng ATL-COM-DAQ-2015-142-fig2.png r1 manage 18.0 K 2015-09-20 - 04:20 TomoeKishimoto  
Unknown file formateps ATL-COM-DAQ-2015-142-fig3.eps r1 manage 12.4 K 2015-09-20 - 04:20 TomoeKishimoto  
PNGpng ATL-COM-DAQ-2015-142-fig3.png r1 manage 24.5 K 2015-09-20 - 04:20 TomoeKishimoto  
PDFpdf ATL-COM-DAQ-2015-201-fig1.pdf r1 manage 26.4 K 2015-11-30 - 17:48 MasatoAoki  
PNGpng ATL-COM-DAQ-2015-201-fig1.png r1 manage 40.1 K 2015-11-30 - 17:49 MasatoAoki  
PDFpdf ATL-COM-DAQ-2015-201-fig2.pdf r1 manage 18.9 K 2015-11-30 - 17:48 MasatoAoki  
PNGpng ATL-COM-DAQ-2015-201-fig2.png r1 manage 30.5 K 2015-11-30 - 17:49 MasatoAoki  
PDFpdf ATL-COM-DAQ-2015-201-fig3.pdf r1 manage 17.9 K 2015-11-30 - 17:48 MasatoAoki  
PNGpng ATL-COM-DAQ-2015-201-fig3.png r1 manage 29.7 K 2015-11-30 - 17:49 MasatoAoki  
PDFpdf ATL-COM-DAQ-2015-201-fig4.pdf r1 manage 18.3 K 2015-11-30 - 17:48 MasatoAoki  
PNGpng ATL-COM-DAQ-2015-201-fig4.png r1 manage 30.6 K 2015-11-30 - 17:49 MasatoAoki  
PDFpdf ATL-COM-DAQ-2015-201-fig5.pdf r1 manage 14.8 K 2015-11-30 - 17:48 MasatoAoki  
PNGpng ATL-COM-DAQ-2015-201-fig5.png r1 manage 44.5 K 2015-11-30 - 17:49 MasatoAoki  
PDFpdf ATL-COM-DAQ-2015-201-fig6.pdf r1 manage 14.9 K 2015-11-30 - 17:48 MasatoAoki  
PNGpng ATL-COM-DAQ-2015-201-fig6.png r1 manage 46.3 K 2015-11-30 - 17:49 MasatoAoki  
PDFpdf ATL-COM-DAQ-2015-205-fig1.pdf r1 manage 34.7 K 2016-12-12 - 19:39 MasayaIshino  
PNGpng ATL-COM-DAQ-2015-205-fig1.png r1 manage 282.5 K 2016-12-12 - 19:39 MasayaIshino  
PDFpdf ATL-COM-DAQ-2015-205-fig2.pdf r1 manage 30.2 K 2016-12-12 - 19:39 MasayaIshino  
PNGpng ATL-COM-DAQ-2015-205-fig2.png r1 manage 274.5 K 2016-12-12 - 19:39 MasayaIshino  
PDFpdf ATL-COM-DAQ-2015-205-fig3.pdf r1 manage 34.1 K 2016-12-12 - 19:39 MasayaIshino  
PNGpng ATL-COM-DAQ-2015-205-fig3.png r1 manage 489.6 K 2016-12-12 - 19:39 MasayaIshino  
PDFpdf ATL-COM-DAQ-2015-205-fig4.pdf r1 manage 29.4 K 2016-12-12 - 19:39 MasayaIshino  
PNGpng ATL-COM-DAQ-2015-205-fig4.png r1 manage 307.2 K 2016-12-12 - 19:39 MasayaIshino  
PDFpdf ATL-COM-DAQ-2015-205-fig5.pdf r1 manage 29.2 K 2016-12-12 - 19:39 MasayaIshino  
PNGpng ATL-COM-DAQ-2015-205-fig5.png r1 manage 271.2 K 2016-12-12 - 19:39 MasayaIshino  
PDFpdf ATL-COM-DAQ-2015-205-fig6.pdf r1 manage 28.4 K 2016-12-12 - 19:40 MasayaIshino  
PNGpng ATL-COM-DAQ-2015-205-fig6.png r1 manage 306.6 K 2016-12-12 - 19:40 MasayaIshino  
Unknown file formateps ATL-COM-DAQ-2017-022-fig1a.eps r1 manage 19.4 K 2017-05-07 - 13:12 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2017-022-fig1a.pdf r1 manage 16.0 K 2017-05-07 - 13:12 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2017-022-fig1a.png r1 manage 18.0 K 2017-05-07 - 13:12 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2017-022-fig1b.eps r1 manage 16.9 K 2017-05-07 - 13:12 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2017-022-fig1b.pdf r1 manage 15.5 K 2017-05-07 - 13:12 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2017-022-fig1b.png r1 manage 17.5 K 2017-05-07 - 13:12 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2017-022-fig2.eps r1 manage 13.3 K 2017-05-07 - 13:12 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2017-022-fig2.pdf r1 manage 16.4 K 2017-05-07 - 13:12 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2017-022-fig2.png r1 manage 20.7 K 2017-05-07 - 13:12 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2017-022-fig3.eps r1 manage 16.8 K 2017-05-07 - 13:12 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2017-022-fig3.pdf r1 manage 17.0 K 2017-05-07 - 13:13 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2017-022-fig3.png r1 manage 26.3 K 2017-05-07 - 13:13 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2017-112-1.eps r1 manage 18.2 K 2017-09-15 - 15:28 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2017-112-1.pdf r1 manage 18.4 K 2017-09-15 - 15:28 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2017-112-1.png r1 manage 21.8 K 2017-09-15 - 15:28 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2017-112-2.eps r1 manage 12.8 K 2017-09-15 - 15:28 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2017-112-2.pdf r1 manage 17.8 K 2017-09-15 - 15:28 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2017-112-2.png r1 manage 20.7 K 2017-09-15 - 15:28 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2018-008-1D_eff_17_16_MU10.eps r1 manage 9.5 K 2018-02-18 - 20:18 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-1D_eff_17_16_MU10.pdf r1 manage 44.3 K 2018-02-18 - 20:18 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-1D_eff_17_16_MU10.png r1 manage 7.6 K 2018-02-18 - 20:18 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-1D_eff_17_16_MU11.eps r1 manage 9.5 K 2018-02-18 - 20:18 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-1D_eff_17_16_MU11.pdf r1 manage 44.3 K 2018-02-18 - 20:18 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-1D_eff_17_16_MU11.png r1 manage 7.6 K 2018-02-18 - 20:18 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-BCtiming.eps r1 manage 20.0 K 2018-02-18 - 20:18 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-BCtiming.pdf r1 manage 336.4 K 2018-02-18 - 20:18 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-BCtiming.png r1 manage 28.2 K 2018-02-18 - 20:18 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-effratio_2017over2016_MU10.eps r1 manage 40.0 K 2018-02-18 - 20:20 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-effratio_2017over2016_MU10.pdf r1 manage 466.8 K 2018-02-18 - 20:20 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-effratio_2017over2016_MU10.png r1 manage 32.1 K 2018-02-18 - 20:20 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-effratio_2017over2016_MU11.eps r1 manage 41.9 K 2018-02-18 - 20:20 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-effratio_2017over2016_MU11.pdf r1 manage 465.3 K 2018-02-18 - 20:20 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-effratio_2017over2016_MU11.png r1 manage 34.5 K 2018-02-18 - 20:20 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-plateaueff_vs_days.eps r1 manage 23.3 K 2018-02-18 - 20:20 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-plateaueff_vs_days.pdf r1 manage 55.2 K 2018-02-18 - 20:20 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-plateaueff_vs_days.png r1 manage 27.8 K 2018-02-18 - 20:20 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-sector12_mu10.eps r1 manage 20.0 K 2018-02-18 - 20:21 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-sector12_mu10.pdf r1 manage 219.4 K 2018-02-18 - 20:21 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-sector12_mu10.png r1 manage 18.7 K 2018-02-18 - 20:21 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-sector12_mu11.eps r1 manage 20.0 K 2018-02-18 - 20:21 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-sector12_mu11.pdf r1 manage 197.8 K 2018-02-18 - 20:21 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-sector12_mu11.png r1 manage 19.0 K 2018-02-18 - 20:21 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-sector14_mu10.eps r1 manage 19.9 K 2018-02-18 - 20:21 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-sector14_mu10.pdf r1 manage 223.1 K 2018-02-18 - 20:21 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-sector14_mu10.png r1 manage 18.9 K 2018-02-18 - 20:21 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-sector14_mu11.eps r1 manage 19.9 K 2018-02-18 - 20:21 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-sector14_mu11.pdf r1 manage 195.0 K 2018-02-18 - 20:21 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-sector14_mu11.png r1 manage 19.1 K 2018-02-18 - 20:21 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-time_vs_days.eps r1 manage 23.2 K 2018-02-18 - 20:21 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-time_vs_days.pdf r1 manage 58.2 K 2018-02-18 - 20:21 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-time_vs_days.png r1 manage 11.8 K 2018-02-18 - 20:21 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-008-turnon.eps r1 manage 15.5 K 2018-02-18 - 20:21 JoergStelzer  
PDFpdf ATL-COM-DAQ-2018-008-turnon.pdf r1 manage 60.1 K 2018-02-18 - 20:21 JoergStelzer  
PNGpng ATL-COM-DAQ-2018-008-turnon.png r1 manage 23.2 K 2018-02-18 - 20:21 JoergStelzer  
Unknown file formateps ATL-COM-DAQ-2018-033-fig1.eps r1 manage 24.1 K 2018-05-28 - 04:43 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2018-033-fig1.pdf r1 manage 17.0 K 2018-05-28 - 04:43 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2018-033-fig1.png r1 manage 14.8 K 2018-05-28 - 04:43 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2018-033-fig2.eps r1 manage 75.5 K 2018-05-28 - 04:43 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2018-033-fig2.pdf r1 manage 43.4 K 2018-05-28 - 04:43 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2018-033-fig2.png r1 manage 23.5 K 2018-05-28 - 04:43 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2018-181-fig1_BC0HighPtFractionTime.eps r1 manage 26.8 K 2018-12-20 - 05:05 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2018-181-fig1_BC0HighPtFractionTime.pdf r1 manage 25.7 K 2018-12-20 - 05:05 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2018-181-fig1_BC0HighPtFractionTime.png r1 manage 29.0 K 2018-12-20 - 05:05 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2018-181-fig2_TriggerEffPt.eps r1 manage 25.7 K 2018-12-20 - 05:08 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2018-181-fig2_TriggerEffPt.pdf r1 manage 22.6 K 2018-12-20 - 05:08 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2018-181-fig2_TriggerEffPt.png r1 manage 26.7 K 2018-12-20 - 05:08 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2018-181-fig3_TriggerEffTime.eps r1 manage 23.1 K 2018-12-20 - 09:38 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2018-181-fig3_TriggerEffTime.pdf r1 manage 43.6 K 2018-12-20 - 09:38 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2018-181-fig3_TriggerEffTime.png r1 manage 39.9 K 2018-12-20 - 09:38 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2018-181-fig4a_TriggerEffEta.eps r1 manage 20.8 K 2018-12-20 - 11:22 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2018-181-fig4a_TriggerEffEta.pdf r1 manage 19.3 K 2018-12-20 - 11:22 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2018-181-fig4a_TriggerEffEta.png r1 manage 18.8 K 2018-12-20 - 11:22 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2018-181-fig4b_TriggerEffPhi.eps r1 manage 18.2 K 2018-12-20 - 11:22 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2018-181-fig4b_TriggerEffPhi.pdf r1 manage 17.9 K 2018-12-20 - 11:22 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2018-181-fig4b_TriggerEffPhi.png r1 manage 18.3 K 2018-12-20 - 11:22 JumpeiMaeda  
Unknown file formateps ATL-COM-DAQ-2019-021-fig01.eps r1 manage 27.1 K 2019-02-22 - 18:03 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig01.pdf r1 manage 21.1 K 2019-02-22 - 18:03 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig01.png r1 manage 22.9 K 2019-02-22 - 18:03 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig02.eps r1 manage 27.0 K 2019-02-22 - 18:03 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig02.pdf r1 manage 20.9 K 2019-02-22 - 18:03 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig02.png r1 manage 23.1 K 2019-02-22 - 18:03 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig03.eps r1 manage 23.5 K 2019-02-22 - 18:03 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig03.pdf r1 manage 18.3 K 2019-02-22 - 18:03 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig03.png r1 manage 21.5 K 2019-02-22 - 18:03 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig04.eps r1 manage 23.5 K 2019-02-22 - 18:03 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig04.pdf r1 manage 18.3 K 2019-02-22 - 18:03 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig04.png r1 manage 21.6 K 2019-02-22 - 18:03 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig05a.eps r1 manage 24.5 K 2019-02-22 - 18:03 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig05a.pdf r1 manage 18.2 K 2019-02-22 - 18:03 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig05a.png r1 manage 23.1 K 2019-02-22 - 18:03 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig05b.eps r1 manage 24.1 K 2019-02-22 - 18:03 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig05b.pdf r1 manage 18.1 K 2019-02-22 - 18:03 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig05b.png r1 manage 24.9 K 2019-02-22 - 18:03 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig06a.eps r1 manage 28.1 K 2019-02-22 - 18:04 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig06a.pdf r1 manage 20.6 K 2019-02-22 - 18:04 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig06a.png r1 manage 23.2 K 2019-02-22 - 18:04 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig06b.eps r1 manage 27.3 K 2019-02-22 - 18:04 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig06b.pdf r1 manage 20.8 K 2019-02-22 - 18:04 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig06b.png r1 manage 25.1 K 2019-02-22 - 18:04 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig07a.eps r1 manage 29.4 K 2019-02-22 - 18:04 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig07a.pdf r1 manage 21.1 K 2019-02-22 - 18:04 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig07a.png r1 manage 29.1 K 2019-02-22 - 18:04 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig07b.eps r1 manage 29.0 K 2019-02-22 - 18:05 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig07b.pdf r1 manage 21.2 K 2019-02-22 - 18:05 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig07b.png r1 manage 30.2 K 2019-02-22 - 18:05 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig08a.eps r1 manage 5052.0 K 2019-02-22 - 18:05 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig08a.pdf r1 manage 1728.3 K 2019-02-22 - 18:05 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig08a.png r1 manage 98.6 K 2019-02-22 - 18:05 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig08b.eps r1 manage 5742.3 K 2019-02-22 - 18:05 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig08b.pdf r1 manage 1821.3 K 2019-02-22 - 18:05 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig08b.png r1 manage 124.8 K 2019-02-22 - 18:05 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig09a.eps r1 manage 4945.6 K 2019-02-22 - 18:06 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig09a.pdf r1 manage 1708.8 K 2019-02-22 - 18:06 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig09a.png r1 manage 104.1 K 2019-02-22 - 18:06 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig09b.eps r1 manage 5650.5 K 2019-02-22 - 18:06 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig09b.pdf r1 manage 1816.2 K 2019-02-22 - 18:06 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig09b.png r1 manage 150.1 K 2019-02-22 - 18:06 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig10a.eps r1 manage 5024.7 K 2019-02-22 - 18:06 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig10a.pdf r1 manage 1728.2 K 2019-02-22 - 18:06 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig10a.png r1 manage 108.9 K 2019-02-22 - 18:06 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig10b.eps r1 manage 5677.9 K 2019-02-22 - 18:36 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig10b.pdf r1 manage 1823.2 K 2019-02-22 - 18:36 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig10b.png r1 manage 150.1 K 2019-02-22 - 18:36 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig11a.eps r1 manage 4998.0 K 2019-02-22 - 18:36 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig11a.pdf r1 manage 1721.8 K 2019-02-22 - 18:36 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig11a.png r1 manage 105.2 K 2019-02-22 - 18:36 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig11b.eps r1 manage 5616.5 K 2019-02-22 - 18:36 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig11b.pdf r1 manage 1818.4 K 2019-02-22 - 18:36 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig11b.png r1 manage 145.1 K 2019-02-22 - 18:36 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig12a.eps r1 manage 19.6 K 2019-02-22 - 18:37 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig12a.pdf r1 manage 14.6 K 2019-02-22 - 18:37 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig12a.png r1 manage 20.1 K 2019-02-22 - 18:37 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig12b.eps r1 manage 19.0 K 2019-02-22 - 18:37 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig12b.pdf r1 manage 14.7 K 2019-02-22 - 18:37 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig12b.png r1 manage 20.8 K 2019-02-22 - 18:37 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig13a.eps r1 manage 18.8 K 2019-02-22 - 18:37 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig13a.pdf r1 manage 13.8 K 2019-02-22 - 18:37 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig13a.png r1 manage 20.3 K 2019-02-22 - 18:37 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig13b.eps r1 manage 18.4 K 2019-02-22 - 18:37 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig13b.pdf r1 manage 13.9 K 2019-02-22 - 18:37 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig13b.png r1 manage 20.8 K 2019-02-22 - 18:37 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig14.eps r1 manage 25.6 K 2019-02-22 - 18:37 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig14.pdf r1 manage 18.5 K 2019-02-22 - 18:37 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig14.png r1 manage 21.4 K 2019-02-22 - 18:37 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig15.eps r1 manage 39.2 K 2019-02-22 - 18:37 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig15.pdf r1 manage 23.1 K 2019-02-22 - 18:37 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig15.png r1 manage 22.4 K 2019-02-22 - 18:37 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig16.eps r1 manage 17.4 K 2019-02-22 - 18:38 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig16.pdf r1 manage 14.1 K 2019-02-22 - 18:38 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig16.png r1 manage 12.6 K 2019-02-22 - 18:38 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig17.eps r1 manage 17.0 K 2019-02-22 - 18:38 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig17.pdf r1 manage 14.0 K 2019-02-22 - 18:38 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig17.png r1 manage 12.5 K 2019-02-22 - 18:38 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig18.eps r1 manage 17.1 K 2019-02-22 - 18:38 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig18.pdf r1 manage 13.9 K 2019-02-22 - 18:38 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig18.png r1 manage 12.5 K 2019-02-22 - 18:38 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig19.eps r1 manage 17.1 K 2019-02-22 - 18:39 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig19.pdf r1 manage 13.9 K 2019-02-22 - 18:39 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig19.png r1 manage 12.5 K 2019-02-22 - 18:39 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-021-fig20.eps r1 manage 17.4 K 2019-02-22 - 18:39 MasatoAoki  
PDFpdf ATL-COM-DAQ-2019-021-fig20.pdf r1 manage 14.0 K 2019-02-22 - 18:39 MasatoAoki  
PNGpng ATL-COM-DAQ-2019-021-fig20.png r1 manage 12.5 K 2019-02-22 - 18:39 MasatoAoki  
Unknown file formateps ATL-COM-DAQ-2019-086.eps r1 manage 13.7 K 2019-07-09 - 08:44 JumpeiMaeda  
PDFpdf ATL-COM-DAQ-2019-086.pdf r1 manage 16.2 K 2019-07-09 - 08:44 JumpeiMaeda  
PNGpng ATL-COM-DAQ-2019-086.png r1 manage 21.8 K 2019-07-09 - 08:44 JumpeiMaeda  
Unknown file formateps LHCC_Sep2017_sec12_MU10.eps r1 manage 20.0 K 2017-09-13 - 20:51 LidiaDellAsta  
PDFpdf LHCC_Sep2017_sec12_MU10.pdf r1 manage 17.8 K 2017-09-13 - 20:51 LidiaDellAsta  
Unknown file formateps LHCC_Sep2017_sec12_MU11.eps r1 manage 20.0 K 2017-09-13 - 20:51 LidiaDellAsta  
PDFpdf LHCC_Sep2017_sec12_MU11.pdf r1 manage 17.8 K 2017-09-13 - 20:51 LidiaDellAsta  
PNGpng LHCC_Sep2017_sec12_mu10.png r1 manage 14.2 K 2017-09-13 - 20:51 LidiaDellAsta  
PNGpng LHCC_Sep2017_sec12_mu11.png r1 manage 14.1 K 2017-09-13 - 20:51 LidiaDellAsta  
Unknown file formateps LHCC_Sep2017_sec14_MU10.eps r1 manage 20.0 K 2017-09-13 - 20:51 LidiaDellAsta  
PDFpdf LHCC_Sep2017_sec14_MU10.pdf r1 manage 17.8 K 2017-09-13 - 20:51 LidiaDellAsta  
Unknown file formateps LHCC_Sep2017_sec14_MU11.eps r1 manage 20.0 K 2017-09-13 - 21:10 LidiaDellAsta  
PDFpdf LHCC_Sep2017_sec14_MU11.pdf r1 manage 17.8 K 2017-09-13 - 21:10 LidiaDellAsta  
PNGpng LHCC_Sep2017_sec14_mu10.png r1 manage 14.2 K 2017-09-13 - 20:51 LidiaDellAsta  
PNGpng LHCC_Sep2017_sec14_mu11.png r1 manage 14.2 K 2017-09-13 - 21:10 LidiaDellAsta  
Unknown file formateps LHCC_Sep2017_turn_on_2017.eps r1 manage 15.2 K 2017-09-13 - 21:10 LidiaDellAsta  
PDFpdf LHCC_Sep2017_turn_on_2017.pdf r1 manage 17.3 K 2017-09-13 - 21:10 LidiaDellAsta  
PNGpng LHCC_Sep2017_turn_on_2017.png r1 manage 18.6 K 2017-09-13 - 21:10 LidiaDellAsta  
Unknown file formatgz atl-com-daq-2015-205.tar.gz r1 manage 1084.1 K 2016-12-13 - 16:31 MasayaIshino  
Unknown file formateps eff_th3_allsec.eps r1 manage 14.2 K 2017-05-23 - 12:48 LidiaDellAsta  
PDFpdf eff_th3_allsec.pdf r1 manage 14.4 K 2017-05-23 - 12:48 LidiaDellAsta  
PNGpng eff_th3_allsec.png r1 manage 52.7 K 2017-05-23 - 12:48 LidiaDellAsta  
Unknown file formateps eff_th3_sec12.eps r1 manage 19.9 K 2017-05-23 - 12:48 LidiaDellAsta  
PDFpdf eff_th3_sec12.pdf r1 manage 17.5 K 2017-05-23 - 12:48 LidiaDellAsta  
PNGpng eff_th3_sec12.png r1 manage 50.7 K 2017-05-23 - 12:48 LidiaDellAsta  
Unknown file formateps eff_th3_sec14.eps r1 manage 19.9 K 2017-05-23 - 12:49 LidiaDellAsta  
PDFpdf eff_th3_sec14.pdf r1 manage 17.5 K 2017-05-23 - 12:49 LidiaDellAsta  
PNGpng eff_th3_sec14.png r1 manage 50.3 K 2017-05-23 - 12:49 LidiaDellAsta  
PDFpdf fig_01.pdf r1 manage 38.2 K 2016-02-19 - 17:50 LidiaDellAsta  
PNGpng fig_01.png r1 manage 31.1 K 2016-02-19 - 17:50 LidiaDellAsta  
PDFpdf fig_02.pdf r1 manage 39.6 K 2016-02-19 - 17:55 LidiaDellAsta  
PNGpng fig_02.png r1 manage 50.2 K 2016-02-19 - 17:55 LidiaDellAsta  
PDFpdf fig_03.pdf r1 manage 19.7 K 2016-02-19 - 17:55 LidiaDellAsta  
PNGpng fig_03.png r1 manage 21.5 K 2016-02-19 - 17:55 LidiaDellAsta  
PDFpdf fig_04.pdf r1 manage 14.2 K 2016-02-19 - 17:55 LidiaDellAsta  
PNGpng fig_04.png r1 manage 13.1 K 2016-02-19 - 17:55 LidiaDellAsta  
PDFpdf fig_05.pdf r1 manage 18.8 K 2016-02-19 - 17:55 LidiaDellAsta  
PNGpng fig_05.png r1 manage 15.6 K 2016-02-19 - 17:55 LidiaDellAsta  
PDFpdf fig_06.pdf r1 manage 19.6 K 2016-02-19 - 17:55 LidiaDellAsta  
PNGpng fig_06.png r1 manage 15.9 K 2016-02-19 - 17:55 LidiaDellAsta  
PDFpdf fig_07.pdf r1 manage 14.4 K 2016-02-19 - 17:56 LidiaDellAsta  
PNGpng fig_07.png r1 manage 17.2 K 2016-02-19 - 17:56 LidiaDellAsta  
PDFpdf fig_08.pdf r1 manage 15.2 K 2016-02-19 - 17:56 LidiaDellAsta  
PNGpng fig_08.png r1 manage 20.0 K 2016-02-19 - 17:56 LidiaDellAsta  
PDFpdf fig_09.pdf r2 r1 manage 20.6 K 2016-02-19 - 20:49 LidiaDellAsta  
PNGpng fig_09.png r2 r1 manage 17.1 K 2016-02-19 - 20:50 LidiaDellAsta  
PDFpdf fig_10.pdf r1 manage 18.7 K 2016-02-19 - 17:56 LidiaDellAsta  
PNGpng fig_10.png r1 manage 49.3 K 2016-02-19 - 17:56 LidiaDellAsta  
PDFpdf fig_11.pdf r1 manage 17.6 K 2016-02-19 - 17:56 LidiaDellAsta  
PNGpng fig_11.png r1 manage 47.3 K 2016-02-19 - 17:56 LidiaDellAsta  
PDFpdf fig_12.pdf r1 manage 16.4 K 2016-02-19 - 17:56 LidiaDellAsta  
PNGpng fig_12.png r1 manage 19.3 K 2016-02-19 - 17:56 LidiaDellAsta  
PDFpdf fig_13.pdf r1 manage 14.5 K 2016-02-19 - 17:56 LidiaDellAsta  
PNGpng fig_13.png r1 manage 12.6 K 2016-02-19 - 17:56 LidiaDellAsta  
PDFpdf mu20tbp_vs_lumi.pdf r1 manage 217.2 K 2015-11-11 - 11:48 DavidMStrom  
PNGpng mu20tbp_vs_lumi.png r1 manage 139.1 K 2015-11-11 - 11:48 DavidMStrom  
Edit | Attach | Watch | Print version | History: r43 < r42 < r41 < r40 < r39 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r43 - 2019-07-24 - ToshiSumida
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Atlas All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback