Data Quality Information for Data

Introduction
Data Quality
- 2022
- Publication
- Full Run-2 period (2015-2018)
- 2018
- 2017
- 2016
- 2015
- 2013
- 2012
- 2011
- 2010

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 Data Preparation Coordinators in case of questions and/or suggestions.

Data Quality

2022

2022 dataset: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collision physics runs with 25 ns bunch-spacing at √s=13.6 TeV for the 2022 Run-3 period, corresponding to a delivered integrated luminosity of 36 fb−1 and a recorded integrated luminosity of 34 fb−1. Runs with specialized physics goals or non-standard running conditions, amounting to 1.7 fb-1, are not considered and thus not included in the denominator of the efficiency calculation. Dedicated luminosity calibration activities during LHC fills used 0.6% of recorded data in 2022 and are included in the inefficiency. Inefficiencies related to object reconstruction, which amount to 1.3%, are currently included in the overall inefficiency but will be recovered in future reprocessings of the data, as will approximately 0.4% of the data lost from the LAr inefficiency. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the Pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS recording efficiency. The luminosity good for physics is 31 fb−1. It is reduced to 29 fb-1 (26 fb-1) for analyses relying on muon-based (jet- and missing-transverse-momentum-based) triggers due to incorrect detector conditions deployed deployed in 2022. The table corresponds to the DQ tag DetStatus-v109-pro28-04 with lumi tag OflLumi-Run3-003.	pdf file
2022 dataset: Cumulative data quality efficiency versus total integrated luminosity collected by the ATLAS experiment between 2015 and 2022.	pdf file

2022 dataset: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collision physics runs with 25 ns bunch-spacing at √s=13.6 TeV for the 2022 Run-3 period, corresponding to a delivered integrated luminosity of 36 fb−1 and a recorded integrated luminosity of 34 fb−1. Runs with specialized physics goals or non-standard running conditions, amounting to 1.7 fb-1, are not considered and thus not included in the denominator of the efficiency calculation. Dedicated luminosity calibration activities during LHC fills used 0.6% of recorded data in 2022 and are included in the inefficiency. Inefficiencies related to object reconstruction, which amount to 1.3%, are currently included in the overall inefficiency but will be recovered in future reprocessings of the data, as will approximately 0.4% of the data lost from the LAr inefficiency. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the Pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS recording efficiency. The luminosity good for physics is 31 fb−1. It is reduced to 29 fb-1 (26 fb-1) for analyses relying on muon-based (jet- and missing-transverse-momentum-based) triggers due to incorrect detector conditions deployed deployed in 2022.

The table corresponds to the DQ tag DetStatus-v109-pro28-04 with lumi tag OflLumi-Run3-003.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/2022_DQEffTable.png

pdf file

2022 dataset: Cumulative data quality efficiency versus total integrated luminosity collected by the ATLAS experiment between 2015 and 2022.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/2022_intdqeffvslumi.png

pdf file

Publication

ATLAS data quality operations and performance for 2015-2018 data-taking : JINST 15 (2020) P04003, arXiv:1911.04632 , ATLAS Twiki

Full Run-2 period (2015-2018)

Full Run-2 dataset: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collisions with 25 ns bunch-spacing at √s=13 TeV for the full Run-2 period (between April 2015; October 2018), corresponding to a delivered integrated luminosity of 153 fb^-1 and a recorded integrated luminosity of 146 fb^-1. Runs with specialized physics goals are not included. Dedicated luminosity calibration activities during LHC fills used 0.6% of recorded data in 2018 and are included in the inefficiency. Trigger specific data quality problems (0.4% inefficiency at Level-1) are included in the overall inefficiency. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag DetStatus-v105-pro22-13 with lumi tag OflLumi-13TeV-010.	pdf file
Full Run-2 dataset: Cumulative data quality efficiency versus total integrated luminosity collected by the ATLAS experiment between 2015 and 2018.	pdf file

Full Run-2 dataset: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collisions with 25 ns bunch-spacing at √s=13 TeV for the full Run-2 period (between April 2015; October 2018), corresponding to a delivered integrated luminosity of 153 fb^-1 and a recorded integrated luminosity of 146 fb^-1. Runs with specialized physics goals are not included. Dedicated luminosity calibration activities during LHC fills used 0.6% of recorded data in 2018 and are included in the inefficiency. Trigger specific data quality problems (0.4% inefficiency at Level-1) are included in the overall inefficiency. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag DetStatus-v105-pro22-13 with lumi tag OflLumi-13TeV-010.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/Run2_DQEffTable.png

pdf file

Full Run-2 dataset: Cumulative data quality efficiency versus total integrated luminosity collected by the ATLAS experiment between 2015 and 2018.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/intdqeffvslumi.png

pdf file

2018

Full 2018 dataset: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collisions at √s=13 TeV between April 25 — October 24 2018, corresponding to a delivered integrated luminosity of 63.8 fb^-1 and a recorded integrated luminosity of 61.7 fb^-1. Dedicated luminosity calibration activities during LHC fills used 0.7% of recorded data and are included in the inefficiency. The luminosity includes 193 pb-1 of good data taken at an average pileup of μ=2.   When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag DetStatus-v102-pro22-04 with lumi tag OflLumi-13TeV-001.	pdf file
2018 dataset to mid-September: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collisions at √s=13 TeV between April 25 — September 10 2018, corresponding to a delivered integrated luminosity of 51.4 fb^-1 and a recorded integrated luminosity of 49.6 fb^-1. Dedicated luminosity calibration activities during LHC fills used 0.7% of recorded data and are included in the inefficiency. The luminosity includes 193 pb-1 of good data taken at an average pileup of μ=2.   When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag DetStatus-v102-pro22-03 with lumi tag OflLumi-13TeV-001.	pdf file

Full 2018 dataset: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collisions at √s=13 TeV between April 25 — October 24 2018, corresponding to a delivered integrated luminosity of 63.8 fb^-1 and a recorded integrated luminosity of 61.7 fb^-1. Dedicated luminosity calibration activities during LHC fills used 0.7% of recorded data and are included in the inefficiency. The luminosity includes 193 pb-1 of good data taken at an average pileup of μ=2.   When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag DetStatus-v102-pro22-04 with lumi tag OflLumi-13TeV-001.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2018pp-AprOct2018.png

pdf file

2018 dataset to mid-September: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collisions at √s=13 TeV between April 25 — September 10 2018, corresponding to a delivered integrated luminosity of 51.4 fb^-1 and a recorded integrated luminosity of 49.6 fb^-1. Dedicated luminosity calibration activities during LHC fills used 0.7% of recorded data and are included in the inefficiency. The luminosity includes 193 pb-1 of good data taken at an average pileup of μ=2.   When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag DetStatus-v102-pro22-03 with lumi tag OflLumi-13TeV-001.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2018pp-AprSep2018.png

pdf file

2018 dataset to mid-August: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collisions at √s=13 TeV between April 25 — August 20 2018, corresponding to a delivered integrated luminosity of 39.2 fb^-1 and a recorded integrated luminosity of 37.7 fb^-1. Dedicated luminosity calibration activities during LHC fills used 0.7% of recorded data and are included in the inefficiency. The luminosity includes 193 pb-1 of good data taken at an average pileup of μ=2.   When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag HEAD with lumi tag OflLumi-13TeV-001.	pdf file
2018 dataset to mid-June: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collisions with 25ns bunch spacing at √s=13 TeV between April 25 and June 11 2018, corresponding to a delivered integrated luminosity of 22.7 fb^-1 and a recorded integrated luminosity of 21.7 fb^-1, after switching the tracking detectors on. Dedicated luminosity calibration activities during LHC fills used 1.0% of recorded data and are included in the inefficiency.   When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag HEAD with lumi tag OflLumi-13TeV-001.	pdf file

2018 dataset to mid-August: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collisions at √s=13 TeV between April 25 — August 20 2018, corresponding to a delivered integrated luminosity of 39.2 fb^-1 and a recorded integrated luminosity of 37.7 fb^-1. Dedicated luminosity calibration activities during LHC fills used 0.7% of recorded data and are included in the inefficiency. The luminosity includes 193 pb-1 of good data taken at an average pileup of μ=2.   When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag HEAD with lumi tag OflLumi-13TeV-001.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2018pp-AprAug2018.png

pdf file

2018 dataset to mid-June: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam in pp collisions with 25ns bunch spacing at √s=13 TeV between April 25 and June 11 2018, corresponding to a delivered integrated luminosity of 22.7 fb^-1 and a recorded integrated luminosity of 21.7 fb^-1, after switching the tracking detectors on. Dedicated luminosity calibration activities during LHC fills used 1.0% of recorded data and are included in the inefficiency.   When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag HEAD with lumi tag OflLumi-13TeV-001.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2018pp-AprJune2018.png

pdf file

2017

2017 Full Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs with 25ns bunch spacing taken between 5th June and 10th November 2016, corresponding to a delivered integrated luminosity of 50.4 fb^-1 and a recorded integrated luminosity of 46.8 fb^-1, are shown.     When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag DetStatus-v97-pro21-13 with lumi tag OflLumi-13TeV-001.	pdf file
2017 Dataset to October: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs with 25ns bunch spacing taken between 5th June and 8th October 2016, corresponding to a recorded integrated luminosity of 30.5 fb^-1, are shown.     When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag DetStatus-v95-pro21-09 with lumi tag OflLumi-13TeV-001.	pdf file

2017 Full Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs with 25ns bunch spacing taken between 5th June and 10th November 2016, corresponding to a delivered integrated luminosity of 50.4 fb^-1 and a recorded integrated luminosity of 46.8 fb^-1, are shown.     When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag DetStatus-v97-pro21-13 with lumi tag OflLumi-13TeV-001.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2017pp-JuneNov2017.png

pdf file

2017 Dataset to October: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs with 25ns bunch spacing taken between 5th June and 8th October 2016, corresponding to a recorded integrated luminosity of 30.5 fb^-1, are shown.     When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and turning on the pre-amplifiers for the pixel system. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag DetStatus-v95-pro21-09 with lumi tag OflLumi-13TeV-001.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2017pp-JuneOct2017.png

pdf file

2016

2016 Full Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs with 25ns bunch spacing taken between 28th April and 26th October 2016, corresponding to a recorded integrated luminosity of 35.9 fb^-1, are shown.     When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag DetStatus-v84-pro20-16 with lumi tag OflLumi-13TeV-005.	pdf file
2016 ICHEP Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs with 25ns bunch spacing taken between 28th April and 10th July 2016, corresponding to a recorded integrated luminosity of 11.0 fb^-1, are shown.     When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag DetStatus-v80-pro20-08 with lumi tag OflLumi-13TeV-005.	pdf file

2016 Full Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs with 25ns bunch spacing taken between 28th April and 26th October 2016, corresponding to a recorded integrated luminosity of 35.9 fb^-1, are shown.     When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag DetStatus-v84-pro20-16 with lumi tag OflLumi-13TeV-005.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2016.png

pdf file

2016 ICHEP Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs with 25ns bunch spacing taken between 28th April and 10th July 2016, corresponding to a recorded integrated luminosity of 11.0 fb^-1, are shown.     When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag DetStatus-v80-pro20-08 with lumi tag OflLumi-13TeV-005.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2016-ICHEP-july2016.png

pdf file

2015

2015 EOYE Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs with 25ns bunch spacing taken between August and November 2015, corresponding to a recorded integrated luminosity of 3.7 fb^-1, are shown.     An additional 0.1 fb^-1 of 50ns bunch spacing data is not shown. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag DetStatus-v73-pro19-08 with lumi tag OflLumi-13TeV-003.	pdf file
LHCP Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs between 3 June and 23 July 2015, corresponding to a recorded integrated luminosity of 173 pb^-1, are shown.     An additional 22 pb^-1 of data recorded in special conditions for detector calibration purposes is not shown. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag DetStatus-v63-pro18 for data15_13TeV periods A,B, and C2-5 and DQ tag DetStatus-v64-pro19 for periods D3-6 with lumi tag OflLumi-13TeV-001.	pdf file
EPS Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs between 3 June and 16 July 2015, corresponding to a recorded integrated luminosity of 91 pb^-1, are shown.     An additional 4 pb^-1 of data recorded in special conditions for detector calibration purposes is not shown. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The all good for physics efficiency includes additional requirements beyond the detector-related efficiencies shown here. The table corresponds to the DQ tag DetStatus-v63-pro18 for data15_13TeV periods A,B, and C2-5 with lumi tag OflLumi-13TeV-001.	pdf file

2013

Full 2013 p-Pb collisions dataset: Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √sNN=5 TeV, and after switching the tracking detectors on. Runs between January 20th and February 10th, corresponding to a recorded integrated luminosity of 29.9 nb-1, are accounted. Data taken up to February 1st was taken in beam1=p and beam2=Pb configuration, data from February 2nd was taken in beam1=Pb and beam2=p configuration. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiency of the CSC system is due to sporadic failures of the sub-detector read-out system during a period of 5 days. The CSC defects affect muons with \|η\|>2.0. The table corresponds to the DQ tag DetStatus-v60-pro15 for data13_hip periods A-B.

Full 2013 p-Pb collisions dataset: Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √sNN=5 TeV, and after switching the tracking detectors on. Runs between January 20th and February 10th, corresponding to a recorded integrated luminosity of 29.9 nb-1, are accounted. Data taken up to February 1st was taken in beam1=p and beam2=Pb configuration, data from February 2nd was taken in beam1=Pb and beam2=p configuration.

When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The inefficiency of the CSC system is due to sporadic failures of the sub-detector read-out system during a period of 5 days. The CSC defects affect muons with |η|>2.0.

The table corresponds to the DQ tag DetStatus-v60-pro15 for data13_hip periods A-B.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table2013hip-JanuaryFebruary2013.png

2012

Full 2012 pp collisions dataset: Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=8 TeV, and after switching the tracking detectors on. Runs between April 4th and December 6th, corresponding to a recorded integrated luminosity of 21.3 fb-1, are accounted. Dat taken up to November 10th were reprocessed with improved conditions. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. At the beginning of 2012 this applied to the SCT and pixel detector, but from June 1st 2012 the configuration was changed to only include the pixel detector in the warm start and account for any longer ramp-up time by the SCT in the DQ efficiency. The inefficiency due to this 'warm-start', as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The table corresponds to the DQ tag DetStatus-v61-pro14-02 for data12_8TeV periods A-L.
HCP dataset: Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=8 TeV, and after switching the tracking detectors on. Runs between April 4th and September 17th, corresponding to a recorded integrated luminosity of 14.0 fb-1, are accounted. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. At the beginning of 2012 this applied to the SCT and pixel detector, but from June 1st 2012 the configuration was changed to only include the pixel detector in the warm start and account for any longer ramp-up time by the SCT in the DQ efficiency. The inefficiency due to this 'warm-start', as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to noise bursts and highly noisy cells (both recoverable in the future) and to isolated HV trips. The table corresponds to the DQ tag DetStatus-v53-pro13 for data12_8TeV periods A1-E5.
ICHEP dataset: Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=8 TeV, and after switching the tracking detectors on. Runs between April 4th and June 18th, corresponding to a recorded integrated luminosity of 6.3 fb-1, are accounted. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. At the beginning of 2012 this applied to the SCT and pixel detector, but from June 1st 2012 the configuration was changed to only include the pixel detector in the warm start and account for any longer ramp-up time by the SCT in the DQ efficiency. The inefficiency due to this 'warm-start', as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to noise bursts and highly noisy cells (both recoverable in the future) and to isolated HV trips. The table corresponds to the DQ tag DetStatus-v47-pro13 for data12_8TeV periods A1-B14.

Full 2012 pp collisions dataset: Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=8 TeV, and after switching the tracking detectors on. Runs between April 4th and December 6th, corresponding to a recorded integrated luminosity of 21.3 fb-1, are accounted. Dat taken up to November 10th were reprocessed with improved conditions.

When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. At the beginning of 2012 this applied to the SCT and pixel detector, but from June 1st 2012 the configuration was changed to only include the pixel detector in the warm start and account for any longer ramp-up time by the SCT in the DQ efficiency. The inefficiency due to this 'warm-start', as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag DetStatus-v61-pro14-02 for data12_8TeV periods A-L.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table2012pp-AprilDecember2012.png

HCP dataset: Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=8 TeV, and after switching the tracking detectors on. Runs between April 4th and September 17th, corresponding to a recorded integrated luminosity of 14.0 fb-1, are accounted.

When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. At the beginning of 2012 this applied to the SCT and pixel detector, but from June 1st 2012 the configuration was changed to only include the pixel detector in the warm start and account for any longer ramp-up time by the SCT in the DQ efficiency. The inefficiency due to this 'warm-start', as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to noise bursts and highly noisy cells (both recoverable in the future) and to isolated HV trips.

The table corresponds to the DQ tag DetStatus-v53-pro13 for data12_8TeV periods A1-E5.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2012-HCP_sept2012.png

ICHEP dataset: Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=8 TeV, and after switching the tracking detectors on. Runs between April 4th and June 18th, corresponding to a recorded integrated luminosity of 6.3 fb-1, are accounted.

When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. At the beginning of 2012 this applied to the SCT and pixel detector, but from June 1st 2012 the configuration was changed to only include the pixel detector in the warm start and account for any longer ramp-up time by the SCT in the DQ efficiency. The inefficiency due to this 'warm-start', as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to noise bursts and highly noisy cells (both recoverable in the future) and to isolated HV trips.

The table corresponds to the DQ tag DetStatus-v47-pro13 for data12_8TeV periods A1-B14.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2012_ICHEP_june2012.png

Early 2012 dataset: Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=8 TeV, and after switching the tracking detectors on. Runs between April 4th and May 31st 2012, corresponding to a recorded integrated luminosity of 3.5 fb-1, are accounted. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to noise bursts and highly noisy cells (both recoverable in the future) and to isolated HV trips. The table corresponds to the DQ tag DetStatus-v45-pro13 for data12_8TeV periods A1-B9.

Early 2012 dataset: Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=8 TeV, and after switching the tracking detectors on. Runs between April 4th and May 31st 2012, corresponding to a recorded integrated luminosity of 3.5 fb-1, are accounted.

When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to noise bursts and highly noisy cells (both recoverable in the future) and to isolated HV trips.

The table corresponds to the DQ tag DetStatus-v45-pro13 for data12_8TeV periods A1-B9.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2012-A1toB9-pro13.png

2011

Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 13th and October 30th, corresponding to a preliminary recorded integrated luminosity of 5.23 fb^‐1, are accounted. When the stable beam flag is raised, the tracking detectors undergo a so‐called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. This table reflects the data quality after the reprocessing. The table corresponds to the DQ tag DetStatus-v36-pro10 for periods B-M and DetStatus-v08-pro07 for period A.	Same DQ table but with the LAr components merged and AllGood efficiency as in the 2012 table

Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 13th and October 30th, corresponding to a preliminary recorded integrated luminosity of 5.23 fb^‐1, are accounted.

This table reflects the data quality after the reprocessing.

The table corresponds to the DQ tag DetStatus-v36-pro10 for periods B-M and DetStatus-v08-pro07 for period A.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2011-AtoM-.png

Same DQ table but with the LAr components merged and AllGood efficiency as in the 2012 table

Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS trigger system during LHC fills with stable beams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 13th and October 30th, corresponding to a recorded integrated luminosity of 5.25 fb^-1, are accounted. The slight inefficiency in the High Level jet trigger is due to a misconfiguration associated with specific calorimeter conditions that occurred during two runs. However, all high PT jets were still successfully triggered and recorded. The table corresponds to the DQ tag DetStatus-v18-pro08-v04 for periods B-H and DetStatus-v08-pro07 for period A.

Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS trigger system during LHC fills with stable beams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 13th and October 30th, corresponding to a recorded integrated luminosity of 5.25 fb^-1, are accounted. The slight inefficiency in the High Level jet trigger is due to a misconfiguration associated with specific calorimeter conditions that occurred during two runs. However, all high PT jets were still successfully triggered and recorded.

The table corresponds to the DQ tag DetStatus-v18-pro08-v04 for periods B-H and DetStatus-v08-pro07 for period A.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodBtoM-trigger-tableOnly.png

Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in Pb-Pb collisions at √s=2.76 TeV per nucleon, and after switching the tracking detectors on. Runs between Nov 12th and Dec 7th, corresponding to a preliminary recorded integrated luminosity of 158 ub^‐1, are accounted. When the stable beam flag is raised, the tracking detectors undergo a so‐called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. This table reflects the data quality after the reprocessing. The table corresponds to the DQ tag DetStatus-v37-pro11 for period N.

Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in Pb-Pb collisions at √s=2.76 TeV per nucleon, and after switching the tracking detectors on. Runs between Nov 12th and Dec 7th, corresponding to a preliminary recorded integrated luminosity of 158 ub^‐1, are accounted.

This table reflects the data quality after the reprocessing.

The table corresponds to the DQ tag DetStatus-v37-pro11 for period N.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-2011-hi.png

NB The purpose of this table is to show the improvement in DQ we achieved from software improvements in the release 17 reprocessing. To be shown in conjunction with the table below! Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 13th and June 29th, corresponding to a recorded integrated luminosity of 1.25 fb^‐1, are accounted. When the stable beam flag is raised, the tracking detectors undergo a so‐called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to isolated HV trips and noise bursts. These will partially be recovered in the future. The other small inefficiencies are due to individual isolated problems with a given subdetector. This table is for the Tier0 processing of this data. The purpose of this table is along with the below reprocessing table to show the approximately 7% improvement in DQ efficiency from the LAr from the reprocessing, now that LAr noise bursts are dealt with by an event veto. The table corresponds to the DQ tag DetStatus-v18-pro08-v04 for periods B-H.

NB The purpose of this table is to show the improvement in DQ we achieved from software improvements in the release 17 reprocessing. To be shown in conjunction with the table below!

Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 13th and June 29th, corresponding to a recorded integrated luminosity of 1.25 fb^‐1, are accounted.

When the stable beam flag is raised, the tracking detectors undergo a so‐called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to isolated HV trips and noise bursts. These will partially be recovered in the future. The other small inefficiencies are due to individual isolated problems with a given subdetector.

This table is for the Tier0 processing of this data.

The purpose of this table is along with the below reprocessing table to show the approximately 7% improvement in DQ efficiency from the LAr from the reprocessing, now that LAr noise bursts are dealt with by an event veto.

The table corresponds to the DQ tag DetStatus-v18-pro08-v04 for periods B-H.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2011-AtoK-t0.png

NB The purpose of this table is to show the improvement in DQ we achieved from software improvements in the release 17 reprocessing. To be shown in conjunction with the table above! Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 13th and June 29th, corresponding to a recorded integrated luminosity of 1.25 fb^‐1, are accounted. When the stable beam flag is raised, the tracking detectors undergo a so‐called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to isolated HV trips and noise bursts. These will partially be recovered in the future. The other small inefficiencies are due to individual isolated problems with a given subdetector. This table reflects the data quality after the reprocessing. The purpose of this table is along with the above Tier0 table to show the approximately 7% improvement in DQ efficiency from the LAr from the reprocessing, now that LAr noise bursts are dealt with by an event veto. The table corresponds to the DQ tag DetStatus-v28-pro09 for periods B-H and corresponds to release 17.0.X.Y.

NB The purpose of this table is to show the improvement in DQ we achieved from software improvements in the release 17 reprocessing. To be shown in conjunction with the table above!

Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 13th and June 29th, corresponding to a recorded integrated luminosity of 1.25 fb^‐1, are accounted.

This table reflects the data quality after the reprocessing.

The purpose of this table is along with the above Tier0 table to show the approximately 7% improvement in DQ efficiency from the LAr from the reprocessing, now that LAr noise bursts are dealt with by an event veto.

The table corresponds to the DQ tag DetStatus-v28-pro09 for periods B-H and corresponds to release 17.0.X.Y.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2011-BtoK-repro.png

2010

Luminosity weighted relatIve fractIon of good quality data delivered by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 30th and October 31st, corresponding to a recorded integrated luminosity of 45 pb^‐1, are accounted. When the stable beam flag is raised, the tracking detectors undergo a so‐called "warm start", which includes a ramp of the high‐voltage and, for the pixel system, turning on the preamplifiers. The 2.0% inefficiency due to this, as well as the 4.4% DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to isolated HV trips and noise bursts. These will parIally be recovered in the future. The inefficiency in the CSC is due to 6/16 problemaIc chambers on one side of the detector during a 3‐day period. The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro05-01 for periods A-I.

Luminosity weighted relatIve fractIon of good quality data delivered by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 30th and October 31st, corresponding to a recorded integrated luminosity of 45 pb^‐1, are accounted.

When the stable beam flag is raised, the tracking detectors undergo a so‐called "warm start", which includes a ramp of the high‐voltage and, for the pixel system, turning on the preamplifiers. The 2.0% inefficiency due to this, as well as the 4.4% DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The inefficiencies in the LAr calorimeter are mostly due to isolated HV trips and noise bursts. These will parIally be recovered in the future. The inefficiency in the CSC is due to 6/16 problemaIc chambers on one side of the detector during a 3‐day period.

The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro05-01 for periods A-I.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoI-v2.png

Responsible: Jamie Boyd, Guillaume Unal, Eric Torrence and Paul Laycock
Last reviewed by: Never reviewed

Attachments

Topic attachments
I	Attachment	History	Action	Size	Date	Who
png	BtoH_DQ_repo.png	r1	manage	36.3 K	2011-09-20 - 16:05	JamieBoyd
png	BtoH_DQtier0.png	r1	manage	44.5 K	2011-09-20 - 16:05	JamieBoyd
png	atlas-dq-eff-2011-hi.png	r1	manage	46.6 K	2012-02-07 - 13:25	JamieBoyd
pdf	atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf	r1	manage	136.2 K	2011-12-12 - 15:43	DavidMStrom
png	atlas-dq-eff-pp2011-AtoK-repro.png	r1	manage	48.0 K	2012-02-07 - 13:24	JamieBoyd
png	atlas-dq-eff-pp2011-AtoK-t0.png	r1	manage	56.2 K	2012-02-07 - 13:24	JamieBoyd
png	atlas-dq-eff-pp2011-AtoM.png	r1	manage	46.0 K	2012-02-07 - 13:23	JamieBoyd
png	dqtable_2018_v1_1.png	r1	manage	66.9 K	2018-06-04 - 15:23	PeterOnyisi

Topic revision: r95 - 2023-03-07 - YosukeTakubo

Account
- Log In

- Cern Search
- TWiki Search
- Google Search
Atlas All webs

Edit
Attach

Copyright &© 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback