Difference: RunStatsPublicResults2010 (1 vs. 92)

Revision 922019-09-10 - RosyNikolaidou

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 30 to 30
 pdf file
Added:
>
>
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

Revision 912019-09-03 - RosyNikolaidou

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 15 to 15
 

Data Quality

Added:
>
>

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.

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

2018

Line: 22 to 39
 
Full 2018 dataset: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam
Changed:
<
<
in pp collisions at √s=13 TeV between April 25 — October 24 2018, corresponding to a delivered integrated
>
>
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.
Line: 44 to 61
 
2018 dataset to mid-September: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam
Changed:
<
<
in pp collisions at √s=13 TeV between April 25 — September 10 2018, corresponding to a delivered integrated
>
>
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.
Line: 68 to 85
 
2018 dataset to mid-August: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam
Changed:
<
<
in pp collisions at √s=13 TeV between April 25 — August 20 2018, corresponding to a delivered integrated
>
>
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.

Revision 902019-02-04 - PeterOnyisi

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 171 to 171
 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.

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v80-pro20-08 with lumi tag OflLumi-13TeV-005.
>
>
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

Revision 892018-11-12 - PeterOnyisi

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 20 to 20
 
Changed:
<
<
2018 dataset to mid-June:
>
>
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
Line: 44 to 66
 
Changed:
<
<
2018 dataset to mid-June:
>
>
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

Revision 882018-10-08 - RosyNikolaidou

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 19 to 19
 
Added:
>
>
2018 dataset to mid-June: 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-June: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam

Revision 872018-09-13 - PeterOnyisi

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 21 to 21
 
2018 dataset to mid-June:
Added:
>
>
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. 


Revision 862018-06-30 - JamesFrost

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 20 to 20
 
Changed:
<
<
2018 dataset to mid-May:
>
>
2018 dataset to mid-June:
 Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam
Changed:
<
<
in pp collisions with 25ns bunch spacing at √s=13 TeV between April 25 and May 10 2018, corresponding to a delivered integrated luminosity of 7.1 fb-1 and a recorded integrated luminosity of 6.7 fb-1, after switching the tracking detectors on.. 1.7% of recorded data were used for dedicated luminosity calibration activities during LHC fills.
>
>
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
Line: 32 to 32
 

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

Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2018pp-AprMay2018.png
pdf file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2018pp-AprJune2018.png
pdf file
 

Revision 852018-06-08 - JamesFrost

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 22 to 22
 
2018 dataset to mid-May: Luminosity weighted relative detector uptime and good data quality efficiencies (in %) during stable beam
Changed:
<
<
in pp collisions with 25ns bunch spacing at √s=13 TeV between April 25 &endash; May 10 2018, corresponding to a delivered integrated luminosity of 7.1 fb-1 and a recorded integrated luminosity of 6.7 fb-1. 1.7% of recorded data were used for dedicated luminosity calibration activities during LHC fills., 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. 

>
>
in pp collisions with 25ns bunch spacing at √s=13 TeV between April 25 and May 10 2018, corresponding to a delivered integrated luminosity of 7.1 fb-1 and a recorded integrated luminosity of 6.7 fb-1, after switching the tracking detectors on.. 1.7% of recorded data were used for dedicated luminosity calibration activities during LHC fills.
 
 When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of
Line: 35 to 32
 

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

Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2017pp-JuneNov2017.png
pdf file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2018pp-AprMay2018.png
pdf file
 
Changed:
<
<
>
>
 

2017

Revision 842018-06-04 - PeterOnyisi

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 15 to 15
 

Data Quality

Added:
>
>

2018

2018 dataset to mid-May: 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 &endash; May 10 2018, corresponding to a delivered integrated luminosity of 7.1 fb-1 and a recorded integrated luminosity of 6.7 fb-1. 1.7% of recorded data were used for dedicated luminosity calibration activities during LHC fills., 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 HEAD 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

Line: 415 to 442
 
META FILEATTACHMENT attachment="atlas-dq-eff-pp2011-AtoK-t0.png" attr="" comment="" date="1328617447" name="atlas-dq-eff-pp2011-AtoK-t0.png" path="atlas-dq-eff-pp2011-AtoK-t0.png" size="57579" stream="atlas-dq-eff-pp2011-AtoK-t0.png" tmpFilename="/usr/tmp/CGItemp18667" user="jboyd" version="1"
META FILEATTACHMENT attachment="atlas-dq-eff-pp2011-AtoK-repro.png" attr="" comment="" date="1328617472" name="atlas-dq-eff-pp2011-AtoK-repro.png" path="atlas-dq-eff-pp2011-AtoK-repro.png" size="49112" stream="atlas-dq-eff-pp2011-AtoK-repro.png" tmpFilename="/usr/tmp/CGItemp18676" user="jboyd" version="1"
META FILEATTACHMENT attachment="atlas-dq-eff-2011-hi.png" attr="" comment="" date="1328617517" name="atlas-dq-eff-2011-hi.png" path="atlas-dq-eff-2011-hi.png" size="47766" stream="atlas-dq-eff-2011-hi.png" tmpFilename="/usr/tmp/CGItemp18581" user="jboyd" version="1"
Added:
>
>
META FILEATTACHMENT attachment="dqtable_2018_v1_1.png" attr="" comment="" date="1528118615" name="dqtable_2018_v1_1.png" path="dqtable_2018_v1_1.png" size="68551" user="ponyisi" version="1"

Revision 832017-12-15 - JamesFrost

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 20 to 20
 
Added:
>
>
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

Revision 822017-10-25 - JamesFrost

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 15 to 15
 

Data Quality

Added:
>
>

2017

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

Revision 812016-12-14 - JonasStrandberg

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 18 to 18
 

2016

Changed:
<
<
>
>
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-v80-pro20-08 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:

Revision 802016-07-25 - PaulLaycock

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 25 to 25
 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
Changed:
<
<
tracking detectors on. Runs with 25ns bunch spacing taken between May and July 2016, corresponding
>
>
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

Revision 792016-07-25 - PaulLaycock

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 15 to 15
 

Data Quality

Added:
>
>

2016

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 May and 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

Revision 782016-02-17 - PaulLaycock

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 24 to 24
 2015 EOYE Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC
Changed:
<
<
fills with stable beams in pp collisions at √s=13 TeV, and after switching the
>
>
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. 
 

Line: 34 to 34
 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.

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v73-pro19-08 with lumi tag OflLumi-13TeV-003.
>
>
The table corresponds to the DQ tag DetStatus-v73-pro19-08 with lumi tag OflLumi-13TeV-003.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2015-AugNov-2015.png
pdf file
Line: 46 to 46
 LHCP Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC
Changed:
<
<
fills with stable beams in pp collisions at √s=13 TeV, and after switching the
>
>
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. 
 

Line: 57 to 57
 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.

Changed:
<
<
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.
>
>
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.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2015LHCP-Aug2015.png
pdf file
Line: 69 to 69
 EPS Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC
Changed:
<
<
fills with stable beams in pp collisions at √s=13 TeV, and after switching the
>
>
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. 
 

Line: 82 to 82
 good for physics efficiency includes additional requirements beyond the detector-related efficiencies shown here.

Changed:
<
<
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.
>
>
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.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2015EPS-July2015.png
pdf file
Line: 96 to 96
 
Changed:
<
<
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.
>
>
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.

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v60-pro15 for data13_hip periods A-B.
>
>
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
Line: 116 to 116
 
Changed:
<
<
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.
>
>
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.

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v61-pro14-02 for data12_8TeV periods A-L.
>
>
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
Line: 129 to 129
 
Changed:
<
<
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.  
>
>
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.

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v53-pro13 for data12_8TeV periods A1-E5.
>
>
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
Line: 144 to 144
 
Changed:
<
<
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.  
>
>
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.

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v47-pro13 for data12_8TeV periods A1-B14.
>
>
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
Line: 162 to 162
 
Changed:
<
<
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.  
>
>
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.

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v45-pro13 for data12_8TeV periods A1-B9.
>
>
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
Line: 180 to 180
 
Changed:
<
<
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.
>
>
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.
Line: 198 to 198
 
Luminosity weighted relative fraction of good quality data delivery by the various components
Changed:
<
<
of the ATLAS trigger system during LHC fills with stable beams in pp collisions at √s=7 TeV, and
>
>
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
Line: 216 to 216
 
Changed:
<
<
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.
>
>
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.
Line: 235 to 235
  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!
Changed:
<
<
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.  
>
>
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.
Line: 255 to 255
 
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!
Changed:
<
<
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.  
>
>
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.

Revision 772015-12-15 - PaulLaycock

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 18 to 18
 

2015

Added:
>
>
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.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2015-AugNov-2015.png
pdf file
 
LHCP Dataset:
Line: 285 to 308
 
<!--Please add the name of someone who is responsible for this page so that he/she can be contacted if changes are needed.
The creator's name will be added by default, but this can be replaced if appropriate.
Put the name first, without dashes.-->
Changed:
<
<
Responsible: Jamie Boyd, Guillaume Unal and Eric Torrence
>
>
Responsible: Jamie Boyd, Guillaume Unal, Eric Torrence and Paul Laycock
 
<!--Once this page has been reviewed, please add the name and the date e.g. StephenHaywood - 31 Oct 2006 -->
Last reviewed by: Never reviewed

Revision 762015-08-28 - EricTorrence

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 18 to 18
 

2015

Deleted:
<
<
 
Changed:
<
<
Early 2015 Dataset:
>
>
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.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2015LHCP-Aug2015.png
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
Line: 37 to 59
 good for physics efficiency includes additional requirements beyond the detector-related efficiencies shown here.

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v63-pro18 for data15_13TeV periods A,B, and C2-5 with and lumi tag OflLumi-13TeV-001.
>
>
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.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2015EPS-July2015.png
pdf file

Revision 752015-07-24 - EricTorrence

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png

Changed:
<
<

Data Quality Information for 2010 and 2011 Data

>
>

Data Quality Information for Data

 
<!--optional-->
Line: 15 to 15
 

Data Quality

Added:
>
>

2015

Early 2015 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 and lumi tag OflLumi-13TeV-001.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2015EPS-July2015.png
pdf file
 

2013

Revision 742013-05-31 - LucaFiorini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 41 to 41
 
Changed:
<
<
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.6 fb-1, are accounted. Dat taken up to November 10th were reprocessed with improved conditions.
>
>
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.

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v58-pro14-01 for data12_8TeV periods A-L.
>
>
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

Revision 732013-03-13 - LucaFiorini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 15 to 15
 

Data Quality

Added:
>
>

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.

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

2012

Changed:
<
<
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.6 fb-1, are accounted. Dat taken up to November 10th were reprocessed with improved conditions.
>
>
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.6 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.

Revision 722013-01-27 - GuillaumeUnal

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 18 to 18
 

2012

Added:
>
>
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.6 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-v58-pro14-01 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.  

Revision 712012-09-28 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 20 to 20
 
Changed:
<
<
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.  
>
>
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.
Line: 38 to 53
 
Changed:
<
<
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.  
>
>
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.

Revision 702012-07-04 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 22 to 22
 
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.  
Changed:
<
<
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.
>
>
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.
 

Revision 692012-06-28 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 20 to 20
 
Added:
>
>
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. 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-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

 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.

Line: 47 to 65
 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
Changed:
<
<
Same DQ table but with the LAr components merged as in the 2012 table
>
>
Same DQ table but with the LAr components merged and AllGood efficiency as in the 2012 table
 

Revision 682012-06-12 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 15 to 15
 

Data Quality

Added:
>
>

2012

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

Line: 28 to 46
 

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

Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2011-AtoM-.png
>
>
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 as in the 2012 table
 

Revision 672012-02-28 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 28 to 28
 

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

Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodBtoM-v036pro10_v1.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2011-AtoM-.png
 
Line: 55 to 55
 
Added:
>
>
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.

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!
Line: 69 to 85
 

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

Changed:
<
<
https://twiki.cern.ch/twiki/pub/AtlasPublic/RunStatsPublicResults2010/BtoH_DQtier0.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2011-AtoK-t0.png
 
Line: 88 to 104
 

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

Changed:
<
<
https://twiki.cern.ch/twiki/pub/AtlasPublic/RunStatsPublicResults2010/BtoH_DQ_repo.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2011-BtoK-repro.png
 

Revision 662012-02-07 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 137 to 137
 
Deleted:
<
<
  • atlas-dq-eff-pp2011-AtoM.png:
    atlas-dq-eff-pp2011-AtoM.png
 
Deleted:
<
<
  • atlas-dq-eff-pp2011-AtoK-t0.png:
    atlas-dq-eff-pp2011-AtoK-t0.png

  • atlas-dq-eff-pp2011-AtoK-repro.png:
    atlas-dq-eff-pp2011-AtoK-repro.png

  • atlas-dq-eff-2011-hi.png:
    atlas-dq-eff-2011-hi.png
 
META FILEATTACHMENT attachment="BtoH_DQtier0.png" attr="" comment="" date="1316527518" name="BtoH_DQtier0.png" path="BtoH_DQtier0.png" size="45612" stream="BtoH_DQtier0.png" tmpFilename="/usr/tmp/CGItemp52444" user="jboyd" version="1"
META FILEATTACHMENT attachment="BtoH_DQ_repo.png" attr="" comment="" date="1316527540" name="BtoH_DQ_repo.png" path="BtoH_DQ_repo.png" size="37139" stream="BtoH_DQ_repo.png" tmpFilename="/usr/tmp/CGItemp52490" user="jboyd" version="1"

Revision 652012-02-07 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 137 to 137
 
Added:
>
>
  • atlas-dq-eff-pp2011-AtoM.png:
    atlas-dq-eff-pp2011-AtoM.png

  • atlas-dq-eff-pp2011-AtoK-t0.png:
    atlas-dq-eff-pp2011-AtoK-t0.png

  • atlas-dq-eff-pp2011-AtoK-repro.png:
    atlas-dq-eff-pp2011-AtoK-repro.png

  • atlas-dq-eff-2011-hi.png:
    atlas-dq-eff-2011-hi.png
 
META FILEATTACHMENT attachment="BtoH_DQtier0.png" attr="" comment="" date="1316527518" name="BtoH_DQtier0.png" path="BtoH_DQtier0.png" size="45612" stream="BtoH_DQtier0.png" tmpFilename="/usr/tmp/CGItemp52444" user="jboyd" version="1"
META FILEATTACHMENT attachment="BtoH_DQ_repo.png" attr="" comment="" date="1316527540" name="BtoH_DQ_repo.png" path="BtoH_DQ_repo.png" size="37139" stream="BtoH_DQ_repo.png" tmpFilename="/usr/tmp/CGItemp52490" user="jboyd" version="1"
META FILEATTACHMENT attachment="atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf" attr="" comment="" date="1323701023" name="atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf" path="atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf" size="139514" stream="atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf" tmpFilename="/usr/tmp/CGItemp64136" user="strom" version="1"
Added:
>
>
META FILEATTACHMENT attachment="atlas-dq-eff-pp2011-AtoM.png" attr="" comment="" date="1328617419" name="atlas-dq-eff-pp2011-AtoM.png" path="atlas-dq-eff-pp2011-AtoM.png" size="47083" stream="atlas-dq-eff-pp2011-AtoM.png" tmpFilename="/usr/tmp/CGItemp18669" user="jboyd" version="1"
META FILEATTACHMENT attachment="atlas-dq-eff-pp2011-AtoK-t0.png" attr="" comment="" date="1328617447" name="atlas-dq-eff-pp2011-AtoK-t0.png" path="atlas-dq-eff-pp2011-AtoK-t0.png" size="57579" stream="atlas-dq-eff-pp2011-AtoK-t0.png" tmpFilename="/usr/tmp/CGItemp18667" user="jboyd" version="1"
META FILEATTACHMENT attachment="atlas-dq-eff-pp2011-AtoK-repro.png" attr="" comment="" date="1328617472" name="atlas-dq-eff-pp2011-AtoK-repro.png" path="atlas-dq-eff-pp2011-AtoK-repro.png" size="49112" stream="atlas-dq-eff-pp2011-AtoK-repro.png" tmpFilename="/usr/tmp/CGItemp18676" user="jboyd" version="1"
META FILEATTACHMENT attachment="atlas-dq-eff-2011-hi.png" attr="" comment="" date="1328617517" name="atlas-dq-eff-2011-hi.png" path="atlas-dq-eff-2011-hi.png" size="47766" stream="atlas-dq-eff-2011-hi.png" tmpFilename="/usr/tmp/CGItemp18581" user="jboyd" version="1"

Revision 642012-01-12 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 131 to 131
 
<!--Please add the name of someone who is responsible for this page so that he/she can be contacted if changes are needed.
The creator's name will be added by default, but this can be replaced if appropriate.
Put the name first, without dashes.-->
Changed:
<
<
Responsible: Jamie Boyd, Beate Heinemann and Eric Torrence
>
>
Responsible: Jamie Boyd, Guillaume Unal and Eric Torrence
 
<!--Once this page has been reviewed, please add the name and the date e.g. StephenHaywood - 31 Oct 2006 -->
Last reviewed by: Never reviewed

Revision 632011-12-12 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 47 to 47
 

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

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

Revision 622011-12-12 - DavidMStrom

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 38 to 38
 
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
Changed:
<
<
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. The slight
>
>
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.
Line: 47 to 47
 

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

Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodAtoH-trigger-v1.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf
 
Line: 139 to 139
 
META FILEATTACHMENT attachment="BtoH_DQtier0.png" attr="" comment="" date="1316527518" name="BtoH_DQtier0.png" path="BtoH_DQtier0.png" size="45612" stream="BtoH_DQtier0.png" tmpFilename="/usr/tmp/CGItemp52444" user="jboyd" version="1"
META FILEATTACHMENT attachment="BtoH_DQ_repo.png" attr="" comment="" date="1316527540" name="BtoH_DQ_repo.png" path="BtoH_DQ_repo.png" size="37139" stream="BtoH_DQ_repo.png" tmpFilename="/usr/tmp/CGItemp52490" user="jboyd" version="1"
Added:
>
>
META FILEATTACHMENT attachment="atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf" attr="" comment="" date="1323701023" name="atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf" path="atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf" size="139514" stream="atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf" tmpFilename="/usr/tmp/CGItemp64136" user="strom" version="1"

Revision 612011-11-30 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 32 to 32
 
Deleted:
<
<
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 August 24th, corresponding to a recorded integrated luminosity of 2.54 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-v32-pro09 for periods B-K2 and DetStatus-v08-pro07 for period A.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodBtoK-v032pro09_v2.png

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 August 13th, corresponding to a recorded integrated luminosity of 2.33 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.

The table corresponds to the DQ tag DetStatus-v25-pro08-v06 for periods B-K2 and DetStatus-v08-pro07 for period A.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodAtoK2-v0.png
 
Line: 85 to 55
 
Added:
>
>
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.

Line: 103 to 76
 
Added:
>
>
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.

Revision 602011-11-29 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 20 to 20
 
Changed:
<
<
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 August 24th, corresponding to a recorded integrated luminosity of 2.54 fb‐1, are accounted.
>
>
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.

Added:
>
>

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/2011/DataQuality/atlas-dq-eff-periodBtoM-v036pro10_v1.png
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 August 24th, corresponding to a recorded integrated luminosity of 2.54 fb‐1, are accounted.
 
Added:
>
>
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-v32-pro09 for periods B-K2 and DetStatus-v08-pro07 for period A.

Revision 592011-10-27 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 29 to 29
 

The table corresponds to the DQ tag DetStatus-v32-pro09 for periods B-K2 and DetStatus-v08-pro07 for period A.

Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodBtoK-v032pro09.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodBtoK-v032pro09_v2.png
 

Revision 582011-10-24 - GuillaumeUnal

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 16 to 16
 

Data Quality

2011

Added:
>
>
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 August 24th, corresponding to a recorded integrated luminosity of 2.54 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-v32-pro09 for periods B-K2 and DetStatus-v08-pro07 for period A.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodBtoK-v032pro09.png
 

Revision 572011-09-20 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 50 to 50
 
Added:
>
>
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://twiki.cern.ch/twiki/pub/AtlasPublic/RunStatsPublicResults2010/BtoH_DQtier0.png
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.

https://twiki.cern.ch/twiki/pub/AtlasPublic/RunStatsPublicResults2010/BtoH_DQ_repo.png
 

2010

Line: 92 to 129
 Last reviewed by: Never reviewed
Added:
>
>
META FILEATTACHMENT attachment="BtoH_DQtier0.png" attr="" comment="" date="1316527518" name="BtoH_DQtier0.png" path="BtoH_DQtier0.png" size="45612" stream="BtoH_DQtier0.png" tmpFilename="/usr/tmp/CGItemp52444" user="jboyd" version="1"
META FILEATTACHMENT attachment="BtoH_DQ_repo.png" attr="" comment="" date="1316527540" name="BtoH_DQ_repo.png" path="BtoH_DQ_repo.png" size="37139" stream="BtoH_DQ_repo.png" tmpFilename="/usr/tmp/CGItemp52490" user="jboyd" version="1"

Revision 562011-08-20 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png

Changed:
<
<

Luminosity and Run Statistics Plots for 2010 Beam Data

>
>

Data Quality Information for 2010 and 2011 Data

 
<!--optional-->
Line: 19 to 19
 
Changed:
<
<
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.  
>
>
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 August 13th, corresponding to a recorded integrated luminosity of 2.33 fb‐1, are accounted.  
 
Changed:
<
<
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 Solenoid and Toroid magnets were not operational for a 3-day period at the start 2011 data-taking.
>
>
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.
 

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v18-pro08-v04 for periods B-H and DetStatus-v08-pro07 for period A.
>
>
The table corresponds to the DQ tag DetStatus-v25-pro08-v06 for periods B-K2 and DetStatus-v08-pro07 for period A.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodAtoH-v0.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodAtoK2-v0.png
 

Revision 552011-07-19 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 31 to 31
 
Added:
>
>
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 June 29th, corresponding to a recorded integrated luminosity of 1.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-periodAtoH-trigger-v1.png
 

2010

Revision 542011-07-15 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 19 to 19
 
Changed:
<
<
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 6th, corresponding to a recorded integrated luminosity of 593 pb‐1, are accounted.  
>
>
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 Solenoid and Toroid magnets were not operational for a 3-day period at the start 2011 data-taking.

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v16-pro08 for periods B-G3 and DetStatus-v08-pro07 for period A.
>
>
The table corresponds to the DQ tag DetStatus-v18-pro08-v04 for periods B-H and DetStatus-v08-pro07 for period A.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodAtoG3-v0.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodAtoH-v0.png
 

Revision 532011-06-15 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 13 to 13
 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.
Deleted:
<
<

Publications

Conference Notes

 

Data Quality

2011

Changed:
<
<
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 May 3rd, corresponding to a recorded integrated luminosity of 252 pb‐1, are accounted.  
>
>
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 6th, corresponding to a recorded integrated luminosity of 593 pb‐1, are accounted.  
 
Changed:
<
<
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 1.8% inefficiency due to this, as well as the 3.3% 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 Solenoid and Toroid magnets were not operational for a 3-day period at the start 2011 data-taking.
>
>
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 Solenoid and Toroid magnets were not operational for a 3-day period at the start 2011 data-taking.
 

Changed:
<
<
The table corresponds to the DQ tag DetStatus-v13-pro08 for periods B-E and DetStatus-v08-pro07 for period A.
>
>
The table corresponds to the DQ tag DetStatus-v16-pro08 for periods B-G3 and DetStatus-v08-pro07 for period A.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodAtoE-v0.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodAtoG3-v0.png
 

Revision 522011-05-14 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 25 to 25
 
Deleted:
<
<

Luminosity and Data Taking Summary Information for pp Collisions

Luminosity versus day

 
Deleted:
<
<
Total Integrated Luminosity
Online plot of the cumulative luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for pp collisions at 7 TeV centre-of-mass energy. The delivered luminosity accounts for the luminosity delivered from the start of stable beams until the LHC requests ATLAS to turn the sensitive detector off to allow a beam dump or beam studies. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function. The systematic uncertainty of the luminosity measurement is estimated to be 3.4%, dominated by the uncertainty in the beam current product of 2.9%. The offline luminosity determined recently is 3.6% lower than the online luminosity shown here. The ratio of the recorded to delivered luminosity gives the ATLAS data taking efficiency (weighted by Luminosity) of 93.6%. The inefficiency accounts for the turn-on of the high voltage of the Pixel, SCT and some of the muon detectors (2.0%) and any inefficiencies due to deadtime or due to individual problems with a given subdetector that prevent the ATLAS data taking to proceed (4.4%). An additional 0.8 pb-1 of luminosity was delivered by the LHC between the request for ATLAS to turn off the sensitive detectors and the end of stable beam conditions.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/sumLumiByDay.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
Integrated Luminosity per day
Same as above but not cumulative.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/lumiByDay.png
eps file
logarithmic y-scale version
logarithmic y-scale eps file
Peak Luminosity per day
The maximum instantaneous luminosity versus day delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/peakLumiByDay.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file

Luminosity versus week

 
Changed:
<
<
Total Integrated Luminosity
Cumulative luminosity versus week delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. The definition is identical to the daily luminosity plots above.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/sumLumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
Integrated Luminosity per week
Same as above but not cumulative.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/lumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale eps file
Peak Luminosity per week
The maximum instantaneous luminosity versus week delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/peakLumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file

Data Taking Efficiency and Pileup Interactions

>
>

Data Quality

 
Added:
>
>

2011

 
Deleted:
<
<
Data Taking Efficiency
ATLAS data taking efficiency in 2010. The denominator is the luminosity delivered between the declaration of stable beams and the LHC request to turn the sensitive detectors off to allow a beam dump or beam studies. The numerator is the luminosity recorded by ATLAS. Each bin represents a week. The empty bins are due to weeks in which no stable beams were delivered by the LHC. The efficiency integrated (and weighted by the weekly luminosity) over this data taking period is 93.6%. The inefficiency accounts for the turn-on of the high voltage of the Pixel, SCT and some of the muon detectors (2.0%) and any inefficiencies due to deadtime or due to individual problems with a given subdetector that prevent the ATLAS data taking to proceed (4.4%).
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/recEffByWeek.png
eps file
ATLAS Warm Start
When the stable beam flag is raised, some of the tracking and muon detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. Shown is the time this procedure took after declaring stable beams. The typical time is 5-10’. The occasional spikes are due to either caution e.g. when the background conditions have changed or due to DAQ problems during this procedure that prevented ATLAS going into this “READY” mode.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/readyTimeByFill.png
eps file
 
Changed:
<
<
Number of Interactions per Crossing
The maximum mean number of events per beam crossing versus day. The mean number of events per crossing is calculated from the per bunch luminosity assuming a total inelastic cross section of 71.5 mb. The online luminosity measurement is used for this calculation as for the luminosity plots. Only the maximum value during stable beam periods is shown.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/peakMuByDay.png
eps file
>
>
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 May 3rd, corresponding to a recorded integrated luminosity of 252 pb‐1, are accounted.  
 
Changed:
<
<

Luminosity Summary Information for Pb-Pb (Heavy Ion) Collisions

>
>
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 1.8% inefficiency due to this, as well as the 3.3% 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 Solenoid and Toroid magnets were not operational for a 3-day period at the start 2011 data-taking.
 
Changed:
<
<
Total Integrated Luminosity
Cumulative integrated luminosity versus day delivered to (dark blue), and recorded by ATLAS (light blue) for Heavy Ion (Pb) collisions during stable beams and for 2.76 TeV centre-of-mass energy per nucleon. The delivered luminosity accounts for the luminosity delivered from the start of stable beams until the LHC requests ATLAS to turn the sensitive detector off to allow a beam dump or beam studies. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total Pb-Pb nuclear cross section of 7.65 barn. The detection efficiency of 79%, for the current method used, is obtained from Monte Carlo simulation.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010hi/DataSummary/figs/sumLumiByDay.png
eps file
Integrated Luminosity per day
Same as above but not cumulative.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010hi/DataSummary/figs/lumiByDay.png
eps file
Peak Luminosity per day
The maximum instantaneous luminosity versus day delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010hi/DataSummary/figs/peakLumiByDay.png
eps file
>
>

The table corresponds to the DQ tag DetStatus-v13-pro08 for periods B-E and DetStatus-v08-pro07 for period A.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2011/DataQuality/atlas-dq-eff-periodAtoE-v0.png
 
Changed:
<
<

Data Quality

>
>

2010

 
Line: 186 to 71
 
Deleted:
<
<

Luminosity Plots for Specific LHC Fills

ATLAS instantaneous luminosity
ATLAS instantaneous luminosity profiles as measured online for representative LHC fills with 7 TeV centre-of-mass energy in 2010. The gray shaded curves give the delivered luminosity, the green shaded curves show the delivered luminosity during stable beam conditions allowing ATLAS to turn on their tracking devices, and the yellow shaded curves give the recorded luminosity with the entire detector available. The missing recording at around 10:00 during Fill 1104 was caused by an intermediate removal of the stable beams condition flag by the LHC.

The luminosity values shown have been calibrated with van-der-Meer beam-separation scan data. The error on the luminosity is estimated to be 11%, dominated by the uncertainty in the beam intensities.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1298.png eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1225.png eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1121.png eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1104.png eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1058.png eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png eps file
ATLAS instantaneous luminosity
ATLAS instantaneous luminosity profiles as measured online during four consecutive LHC fills with 7 TeV centre-of-mass energy and stable beams between July 12 and 15, 2010. The gray shaded curves give the delivered luminosity, the green shaded curves show the delivered luminosity during stable beam conditions allowing ATLAS to turn on their tracking devices, and the yellow shaded curves give the recorded luminosity with the entire detector available.

The total time of stable beams during these fills is 41.8 hours. The total delivered (recorded) luminosity is 142.5 nb−1 (138.9 nb−1). The luminosity values given have been calibrated with van-der-Meer beam-separation scan data. The error on the luminosity is estimated to be 11%, dominated by the uncertainty in the beam intensities.

eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumiJuly12-15.png
eps file
Specific Luminosity per BCID
Distribution of the specific luminosity recorded by ATLAS at 7 TeV for different LHC bunches (BCID), averaged over LHC fill 1256. The specific luminosity is defined as the luminosity per bunch and per unit bunch charge, and is inversely proportional to the product of the horizontal and vertical convolved beam sizes at the IP. Due to the fill pattern, of the 25 bunches in each ring, only 16 are colliding in IP1; the background from the bunches that do not collide in ATLAS remains invisible on a linear scale, since it lies almost four orders of magnitude below the actual luminosity. The maximum bunch-to-bunch spread in specific luminosity approaches 40%, implying a variation of almost a factor of 2 in the product of the horizontal and vertical emittances of colliding-bunch pairs.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/fill1256_bcidspec.png
Luminosity per BCID
Time evolution of the bunch-by-bunch instantaneous luminosity recorded by ATLAS at 7 TeV during LHC fill 1257. In this fill there were 16 bunch pairs colliding at the ATLAS interaction point IP1. The difference, at a given time, between the highest- and the lowest-luminosity bunch is a factor of about 1.6, reflecting the variation of bunch currents and emittances along the colliding-bunch trains.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/fill1257_bcthlum.png

Comparisons of Different Methods Measuring the Luminosity

ATLAS instantaneous luminosity comparing LAr, MBTS and LUCID
The ATLAS instantaneous luminosity as determined with the LAr (blue open circles), the LUCID (open squares), and MBTS (red triangles) sub-detectors (ATLAS run 152409). The two plots give the instantaneous luminosity with two different y-scale ranges. The LAr instantaneous luminosity is corrected for the dead time in the data acquisition system, and therefore is an estimate of the LHC delivered luminosity at the ATLAS interaction point. Both the MBTS and the LUCID methods are not affected by data acquisition dead time. For each of these measurements the acceptance is independently calculated using the PYTHIA Monte Carlo simulation of the proton-proton inelastic interactions. The corresponding cross section used to normalize the measurements is 71.5 mb and it includes non-diffractive, single-diffractive, and double-diffractive processes. The systematic uncertainty is dominated by model dependence in the diffractive components of the cross section. An indication of the size of this uncertainty is obtained by comparing PYHTIA and PHOJET which translates into a variation in the luminosity of about 15%. The uncertainty is 100% correlated between methods. The uncorrelated method-dependent systematic uncertainties are of order 5% for LAr, LUCID, and MBTS. The curves show only the statistical error as the systematic uncertainty is time independent. The statistical errors on the plots are not clearly visible as they are small compared to the size of the markers. For this run the estimated delivered luminosity is (75.6 ± 15.1) μ b−1(stat+syst).
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/run152409_absolute_luminosity_0.png
eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/run152409_absolute_luminosity.png
eps file
Measurement of Rate of Events with at least one Track and corresponding Luminosity for fill 1005

First Plot: Rate of events in LHC Fill 1005 with at least one charged primary particle with pT>0.5 GeV/c, |eta|<0.8, versus UTC time (solid markers). Also shown is the raw rate of events with at least one track in this acceptance range (dashed line). The correction factor applied to the raw rate to obtain the charged particle rate is 1.04 +\- 0.017. Error bars represent the statistical uncertainty, the colored bands include both the systematic and statistical uncertainties.

Second Plot: The instantaneous luminosity derived from counting of events with at least one charged primary particle (pT>0.5 GeV/c, |eta|<0.8) for LHC Fill 1005 as a function of UTC time. Pythia MC09 was used for the acceptance and cross-section models after the correction for tracking, vertex and trigger efficiencies. Error bars represent the statistical uncertainty, the colored bands include both the systematic and statistical uncertainties. The systematic uncertainties account for the correction procedure and the dependence on the Monte Carlo models used for the acceptance and cross-sections by comparing the results obtained with Pythia MC09 and Phojet.

Third Plot: The instantaneous luminosity derived from counting of events with at least one charged primary particle (pT>0.5 GeV/c, |eta|<0.8) for LHC Fill 1005 as a function of UTC time (black points) compared with the Van der Meer calibrated ATLAS luminosity measurement (blue triangles). Pythia MC09 was used for the acceptance and cross-section models for the charged particle analysis. Error bars represent the statistical uncertainty, the colored bands include both the systematic and statistical uncertainties. The systematic uncertainties on the charged particle method account for the correction procedure and the dependence on the Monte Carlo models used for the acceptance and cross-sections by comparing the results obtained with Pythia MC09 and Phojet.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/TrackRate.152166.png
eps file

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/TrackLumi.152166.png
eps file

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/TrackLumivsLarLumi.152166_wVdM.png
eps file

Measurement of Rate of Events with at least one Track and corresponding Luminosity for fill 1089

First Plot: Rate of events in LHC Fill 1089 with at least one charged primary particle (pT > 0.5 GeV, |η| < 0.8) versus UTC time for recorded events (black open circles), and corrected for pile-up (red filled circles). The pile-up correction (μ-correction) was performed as detailed in Equation 2 of ATLAS-CONF-2010-060. The error bars include the statistical uncertainty and the 1.7% uncertainty on the track to particle correction factor of 1.04. This fill corresponds to four ATLAS runs, therefore periods in between runs are empty, as well as the period of the van der Meer scan and periods when the Inner Detector was not fully operational.

Second Plot: The cross section measured in LHC Fill 1089 for events with at least one charged primary particle (pT > 0.5 GeV, |η| < 0.8) versus UTC time. The error bars include the statistical uncertainty and the 1.7% uncertainty on the track to particle correction factor of 1.04. The average cross-section is 42.3 ± 0.7 (stat. + sys.) mb. The scale uncertainty of 11% in the luminosity used to calculate the cross section from the event rate is not included. This fill corresponds to four ATLAS runs, therefore periods in between runs are empty, as well as the period of the van der Meer scan and periods when the Inner Detector was not fully operational.

For details on the event selection see also ATLAS-CONF-2010-101.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/fill1089TrkRate.png
eps file

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/fill1089_sigChPart.png
eps file

Detailed plots on the van der Meer scan from October 2010

For a detailed explanation of all the terms please refer to Luminosity Determination in pp Collisions at sqrt(s)=7 TeV Using the ATLAS Detector at the LHC


The following pages show the results of performing a χ2 fit of a double Gaussian plus constant term to the data. A total of 48 fits are performed corresponding to 2 algorithms*2 scans*2 planes*6 BCIDs. The ordinate is the average visible number of inelastic interactions per bunch crossing (BC), μvis, divided by the product of beam intensities at that point, n1n2, which removes sensitivity of the distributions to decaying beam intensities. The black points show this parameter calculated from LUCID raw data as a function of nominal separation in the plane under consideration. Statistical errors bars are shown but are typically smaller than the marker size. The blue dashed line shows the result of the fit to the data points. For LUCID_Event_OR fits are replotted on a log scale to demonstrate that the measured tails are well modelled by the chosen parameterisation. Here only a selection of fit results are shown.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/ORFitResults/x4.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/ORFitResults/x4log.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/ANDFitResults/x4.png
eps file

The fitted nominal separation at the peak of the double Gaussian, x0, is compared by BCID between each algorithm and scan for the horizontal plane.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/Fittedx0.png
eps file

The fitted nominal separation at the peak of the double Gaussian, y0, is compared by BCID between each algorithm and scan for the vertical plane.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/Fittedy0.png
eps file

The measured convoluted horizontal beam size, Σx, is compared by BCID between algorithms and scans.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/FittedCapSigmaX.png
eps file

The measured convoluted horizontal beam size, Σy, is compared by BCID between algorithms and scans.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/FittedCapSigmaY.png
eps file

For all 48 fits to data the calculated χ2/DoF values are plotted to demonstrate the fit quality.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/Chi2perDoF.png
eps file

The fitted peak values of μVIS/(n1n2) at x0 and y0 for the LUCID_Event_OR algorithm are compared by BCID for each scan.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/FittedORPeak.png
eps file

The fitted peak values of μVIS/(n1n2) at x0 and y0 for the LUCID_Event_AND algorithm are compared by BCID for each scan.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/FittedANDPeak.png
eps file
 
Deleted:
<
<


Summary plots of the measured visible cross-sections, σVIS, are shown comparing the results for each scan. There is one comparison plot for LUCID_Event_OR and one for LUCID_Event_AND. In each plot the weighted mean of scan IV (V) is shown as a dotted (dash-dotted) vertical line. The yellow band corresponds to a 0.5% window around the weighted mean of all 12 calculated cross-section values.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/sigma_visOR.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/sigma_visAND.png
eps file

Horizontal and vertical convolved beam sizes obtained from double gaussian fits to bunch-by-bunch van der Meer scan data of the BCM-Event-OR algorithm in LHC fill 1386. Results of the two scans are shown separately indicating a clear broadening due to emittance growth in the vertical plane only. The time between two scans over the same coordinate was 30 minutes. Error bars reflect fit statistics only.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/BCM/SigmaXvsBCID_BCM.png
eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/BCM/SigmaYvsBCID_BCM.png
eps file

The measured convoluted horizontal beam size, Σy, is compared by BCID between algorithms and scans between LUCID and BCM for all bunch crossings.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/CapSigma_BCM_vs_LUCID_x.png
eps file

The measured convoluted vertical beam size, Σy, is compared by BCID between algorithms and scans between LUCID and BCM for all bunch crossings.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/CapSigma_BCM_vs_LUCID_y.png
eps file
 

<!--***********************************************************-->

Revision 512011-04-19 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 15 to 15
 

Publications

Changed:
<
<
>
>
 

Conference Notes

Revision 492011-03-29 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 163 to 163
 
Changed:
<
<
Luminosity weighted relaIve fracIon of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=7 TeV, and a[er switching
>
>
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.

Revision 482011-03-22 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 29 to 29
 
Total Integrated Luminosity
Changed:
<
<
Cumulative luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for pp collisions at 7 TeV centre-of-mass energy. The delivered luminosity accounts for the luminosity delivered from the start of stable beams until the LHC requests ATLAS to turn the sensitive detector off to allow a beam dump or beam studies. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%. The ratio of the recorded to delivered luminosity gives the ATLAS data taking efficiency (weighted by Luminosity) of 93.6%. The inefficiency accounts for the turn-on of the high voltage of the Pixel, SCT and some of the muon detectors (2.0%) and any inefficiencies due to deadtime or due to individual problems with a given subdetector that prevent the ATLAS data taking to proceed (4.4%). An additional 0.8 pb-1 of luminosity was delivered by the LHC between the request for ATLAS to turn off the sensitive detectors and the end of stable beam conditions.
>
>
Online plot of the cumulative luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for pp collisions at 7 TeV centre-of-mass energy. The delivered luminosity accounts for the luminosity delivered from the start of stable beams until the LHC requests ATLAS to turn the sensitive detector off to allow a beam dump or beam studies. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function. The systematic uncertainty of the luminosity measurement is estimated to be 3.4%, dominated by the uncertainty in the beam current product of 2.9%. The offline luminosity determined recently is 3.6% lower than the online luminosity shown here. The ratio of the recorded to delivered luminosity gives the ATLAS data taking efficiency (weighted by Luminosity) of 93.6%. The inefficiency accounts for the turn-on of the high voltage of the Pixel, SCT and some of the muon detectors (2.0%) and any inefficiencies due to deadtime or due to individual problems with a given subdetector that prevent the ATLAS data taking to proceed (4.4%). An additional 0.8 pb-1 of luminosity was delivered by the LHC between the request for ATLAS to turn off the sensitive detectors and the end of stable beam conditions.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByDay.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/sumLumiByDay.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
 
Integrated Luminosity per day
Same as above but not cumulative.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByDay.png
eps file
logarithmic y-scale version
logarithmic y-scale eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/lumiByDay.png
eps file
logarithmic y-scale version
logarithmic y-scale eps file
 
Line: 53 to 53
 
Peak Luminosity per day
The maximum instantaneous luminosity versus day delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByDay.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/peakLumiByDay.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
 
Line: 67 to 67
 
Total Integrated Luminosity
Cumulative luminosity versus week delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. The definition is identical to the daily luminosity plots above.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/sumLumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
 
Integrated Luminosity per week
Same as above but not cumulative.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/lumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale eps file
 
Line: 88 to 88
 
Peak Luminosity per week
The maximum instantaneous luminosity versus week delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/peakLumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
 
Line: 102 to 102
 
Data Taking Efficiency
ATLAS data taking efficiency in 2010. The denominator is the luminosity delivered between the declaration of stable beams and the LHC request to turn the sensitive detectors off to allow a beam dump or beam studies. The numerator is the luminosity recorded by ATLAS. Each bin represents a week. The empty bins are due to weeks in which no stable beams were delivered by the LHC. The efficiency integrated (and weighted by the weekly luminosity) over this data taking period is 93.6%. The inefficiency accounts for the turn-on of the high voltage of the Pixel, SCT and some of the muon detectors (2.0%) and any inefficiencies due to deadtime or due to individual problems with a given subdetector that prevent the ATLAS data taking to proceed (4.4%).
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/recEffByWeek.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/recEffByWeek.png
eps file
 
Line: 111 to 111
 When the stable beam flag is raised, some of the tracking and muon detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. Shown is the time this procedure took after declaring stable beams. The typical time is 5-10’. The occasional spikes are due to either caution e.g. when the background conditions have changed or due to DAQ problems during this procedure that prevented ATLAS going into this “READY” mode.

Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/readyTimeByFill.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/readyTimeByFill.png
eps file
 
Line: 120 to 120
 
Number of Interactions per Crossing
The maximum mean number of events per beam crossing versus day. The mean number of events per crossing is calculated from the per bunch luminosity assuming a total inelastic cross section of 71.5 mb. The online luminosity measurement is used for this calculation as for the luminosity plots. Only the maximum value during stable beam periods is shown.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakMuByDay.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataSummary/figs/peakMuByDay.png
eps file
 

Revision 462011-02-04 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 337 to 337
 

Detailed plots on the van der Meer scan from October 2010

Changed:
<
<
>
>
For a detailed explanation of all the terms please refer to Luminosity Determination in pp Collisions at sqrt(s)=7 TeV Using the ATLAS Detector at the LHC
 
Added:
>
>


The following pages show the results of performing a χ2 fit of a double Gaussian plus constant term to the data. A total of 48 fits are performed corresponding to 2 algorithms*2 scans*2 planes*6 BCIDs. The ordinate is the average visible number of inelastic interactions per bunch crossing (BC), μvis, divided by the product of beam intensities at that point, n1n2, which removes sensitivity of the distributions to decaying beam intensities. The black points show this parameter calculated from LUCID raw data as a function of nominal separation in the plane under consideration. Statistical errors bars are shown but are typically smaller than the marker size. The blue dashed line shows the result of the fit to the data points. For LUCID_Event_OR fits are replotted on a log scale to demonstrate that the measured tails are well modelled by the chosen parameterisation. Here only a selection of fit results are shown.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/ORFitResults/x4.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/ORFitResults/x4log.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/ANDFitResults/x4.png
eps file

The fitted nominal separation at the peak of the double Gaussian, x0, is compared by BCID between each algorithm and scan for the horizontal plane.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/Fittedx0.png
eps file

The fitted nominal separation at the peak of the double Gaussian, y0, is compared by BCID between each algorithm and scan for the vertical plane.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/Fittedy0.png
eps file

The measured convoluted horizontal beam size, Σx, is compared by BCID between algorithms and scans.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/FittedCapSigmaX.png
eps file

The measured convoluted horizontal beam size, Σy, is compared by BCID between algorithms and scans.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/FittedCapSigmaY.png
eps file

For all 48 fits to data the calculated χ2/DoF values are plotted to demonstrate the fit quality.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/Chi2perDoF.png
eps file

The fitted peak values of μVIS/(n1n2) at x0 and y0 for the LUCID_Event_OR algorithm are compared by BCID for each scan.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/FittedORPeak.png
eps file

The fitted peak values of μVIS/(n1n2) at x0 and y0 for the LUCID_Event_AND algorithm are compared by BCID for each scan.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/FittedANDPeak.png
eps file
 

Added:
>
>
Summary plots of the measured visible cross-sections, σVIS, are shown comparing the results for each scan. There is one comparison plot for LUCID_Event_OR and one for LUCID_Event_AND. In each plot the weighted mean of scan IV (V) is shown as a dotted (dash-dotted) vertical line. The yellow band corresponds to a 0.5% window around the weighted mean of all 12 calculated cross-section values.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/sigma_visOR.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/sigma_visAND.png
eps file

 Horizontal and vertical convolved beam sizes obtained from double gaussian fits to bunch-by-bunch van der Meer scan data of the BCM-Event-OR algorithm in LHC fill 1386. Results of the two scans are shown separately indicating a clear broadening due to emittance growth in the vertical plane only. The time between two scans over the same coordinate was 30 minutes. Error bars reflect fit statistics only.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/BCM/SigmaXvsBCID_BCM.png
Line: 350 to 461
 eps file
Added:
>
>


The measured convoluted horizontal beam size, Σy, is compared by BCID between algorithms and scans between LUCID and BCM for all bunch crossings.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/CapSigma_BCM_vs_LUCID_x.png
eps file

The measured convoluted vertical beam size, Σy, is compared by BCID between algorithms and scans between LUCID and BCM for all bunch crossings.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/VdmLucid_Oct2010/SummaryPlots/CapSigma_BCM_vs_LUCID_y.png
eps file
 

Revision 452011-01-13 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
AtlasPublicTopicHeader.png
Line: 13 to 13
 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.
Added:
>
>

Publications

 

Conference Notes

Line: 158 to 162
 
Changed:
<
<
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 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 partially be recovered when the data are reprocessed. The inefficiency in the Tile calorimeter arises from an incorrect masking of a channel in a single run which will be fixed for future reprocessings. The inefficiency in the CSC is due to 6/16 problematic chambers on one side of the detector during a 3-day period.

>
>
Luminosity weighted relaIve fracIon of good quality data delivery by the various ATLAS subsystems during LHC fills with stable beams in pp collisions at √s=7 TeV, and a[er 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.

 

Changed:
<
<
The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B, LBSUMM#DetStatus-pass1-analysis-2010X (X=C-I) for periods C-I.
>
>
The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro05-01 for periods A-I.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoI-v1.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoI-v2.png
 
Line: 258 to 270
 
Changed:
<
<
Measurement of Rate of Events with at least one Track and corresponding Luminosity
>
>
Measurement of Rate of Events with at least one Track and corresponding Luminosity for fill 1005
  First Plot: Rate of events in LHC Fill 1005 with at least one charged primary particle with pT>0.5 GeV/c, |eta|<0.8,
Line: 284 to 296
 
Added:
>
>
Measurement of Rate of Events with at least one Track and corresponding Luminosity for fill 1089

First Plot: Rate of events in LHC Fill 1089 with at least one charged primary particle (pT > 0.5 GeV, |η| < 0.8) versus UTC time for recorded events (black open circles), and corrected for pile-up (red filled circles). The pile-up correction (μ-correction) was performed as detailed in Equation 2 of ATLAS-CONF-2010-060. The error bars include the statistical uncertainty and the 1.7% uncertainty on the track to particle correction factor of 1.04. This fill corresponds to four ATLAS runs, therefore periods in between runs are empty, as well as the period of the van der Meer scan and periods when the Inner Detector was not fully operational.

Second Plot: The cross section measured in LHC Fill 1089 for events with at least one charged primary particle (pT > 0.5 GeV, |η| < 0.8) versus UTC time. The error bars include the statistical uncertainty and the 1.7% uncertainty on the track to particle correction factor of 1.04. The average cross-section is 42.3 ± 0.7 (stat. + sys.) mb. The scale uncertainty of 11% in the luminosity used to calculate the cross section from the event rate is not included. This fill corresponds to four ATLAS runs, therefore periods in between runs are empty, as well as the period of the van der Meer scan and periods when the Inner Detector was not fully operational.

For details on the event selection see also ATLAS-CONF-2010-101.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/fill1089TrkRate.png
eps file

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/fill1089_sigChPart.png
eps file

 
Added:
>
>

Detailed plots on the van der Meer scan from October 2010


Horizontal and vertical convolved beam sizes obtained from double gaussian fits to bunch-by-bunch van der Meer scan data of the BCM-Event-OR algorithm in LHC fill 1386. Results of the two scans are shown separately indicating a clear broadening due to emittance growth in the vertical plane only. The time between two scans over the same coordinate was 30 minutes. Error bars reflect fit statistics only.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/BCM/SigmaXvsBCID_BCM.png
eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/BCM/SigmaYvsBCID_BCM.png
eps file
 
Added:
>
>
 

<!--***********************************************************-->

Revision 442011-01-03 - BeateHeinemann

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="AtlasResults"
>
>
META TOPICPARENT name="WebHome"
 AtlasPublicTopicHeader.png
Line: 17 to 17
 
Added:
>
>
 

Luminosity and Data Taking Summary Information for pp Collisions

Luminosity versus day

Line: 297 to 298
 
<!--Please add the name of someone who is responsible for this page so that he/she can be contacted if changes are needed.
The creator's name will be added by default, but this can be replaced if appropriate.
Put the name first, without dashes.-->
Changed:
<
<
Responsible: Andreas Hoecker, Beate Heinemann and Eric Torrence
>
>
Responsible: Jamie Boyd, Beate Heinemann and Eric Torrence
 
<!--Once this page has been reviewed, please add the name and the date e.g. StephenHaywood - 31 Oct 2006 -->
Last reviewed by: Never reviewed

Revision 432010-12-06 - PatrickJussel

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
AtlasPublicTopicHeader.png
Line: 165 to 165
 The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B, LBSUMM#DetStatus-pass1-analysis-2010X (X=C-I) for periods C-I.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Atlas.DataQuality/atlas-on-and-dq-eff-periodAtoI-v1.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoI-v1.png
 

Revision 422010-12-06 - PatrickJussel

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Changed:
<
<
No permission to view Atlas.AtlasPublicTopic
<!--  
  • Set DENYTOPICVIEW =
  • Set ALLOWTOPICCHANGE = atlas-readaccess-current-physicists
-->
>
>
AtlasPublicTopicHeader.png
 

Luminosity and Run Statistics Plots for 2010 Beam Data

Line: 169 to 165
 The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B, LBSUMM#DetStatus-pass1-analysis-2010X (X=C-I) for periods C-I.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoI-v1.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Atlas.DataQuality/atlas-on-and-dq-eff-periodAtoI-v1.png
 

Revision 412010-11-23 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 133 to 133
 of stable beams until the LHC requests ATLAS to turn the sensitive detector off to allow a beam dump or beam studies. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total Pb-Pb nuclear cross section of 7.65 barn. The detection efficiency of 79%, for the current method used, is obtained from Monte Carlo simulation.

Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/HI/figs/sumLumiByDay.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010hi/DataSummary/figs/sumLumiByDay.png
eps file
 
Integrated Luminosity per day
Same as above but not cumulative.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/HI/figs/lumiByDay.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010hi/DataSummary/figs/lumiByDay.png
eps file
 
Line: 150 to 150
 
Peak Luminosity per day
The maximum instantaneous luminosity versus day delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/HI/figs/peakLumiByDay.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010hi/DataSummary/figs/peakLumiByDay.png
eps file
 

Revision 402010-11-16 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 22 to 22
 
Changed:
<
<

Luminosity Summary Information

Versus day

>
>

Luminosity and Data Taking Summary Information for pp Collisions

Luminosity versus day

 
Total Integrated Luminosity
Changed:
<
<
Cumulative luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
>
>
Cumulative luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for pp collisions at 7 TeV centre-of-mass energy. The delivered luminosity accounts for the luminosity delivered from the start of stable beams until the LHC requests ATLAS to turn the sensitive detector off to allow a beam dump or beam studies. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%. The ratio of the recorded to delivered luminosity gives the ATLAS data taking efficiency (weighted by Luminosity) of 93.6%. The inefficiency accounts for the turn-on of the high voltage of the Pixel, SCT and some of the muon detectors (2.0%) and any inefficiencies due to deadtime or due to individual problems with a given subdetector that prevent the ATLAS data taking to proceed (4.4%). An additional 0.8 pb-1 of luminosity was delivered by the LHC between the request for ATLAS to turn off the sensitive detectors and the end of stable beam conditions.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByDay.png
eps file
Line: 37 to 38
 
Integrated Luminosity per day
Changed:
<
<
Integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
>
>
Same as above but not cumulative.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByDay.png
eps file
Line: 58 to 59
 
Changed:
<
<

Versus week

>
>

Luminosity versus week

 
Total Integrated Luminosity
Changed:
<
<
Cumulative luminosity versus week delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
>
>
Cumulative luminosity versus week delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. The definition is identical to the daily luminosity plots above.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByWeek.png
eps file
Line: 72 to 73
 
Integrated Luminosity per week
Changed:
<
<
Integrated luminosity versus week delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
>
>
Same as above but not cumulative.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByWeek.png
eps file
Line: 93 to 94
 
Added:
>
>

Data Taking Efficiency and Pileup Interactions

Data Taking Efficiency
ATLAS data taking efficiency in 2010. The denominator is the luminosity delivered between the declaration of stable beams and the LHC request to turn the sensitive detectors off to allow a beam dump or beam studies. The numerator is the luminosity recorded by ATLAS. Each bin represents a week. The empty bins are due to weeks in which no stable beams were delivered by the LHC. The efficiency integrated (and weighted by the weekly luminosity) over this data taking period is 93.6%. The inefficiency accounts for the turn-on of the high voltage of the Pixel, SCT and some of the muon detectors (2.0%) and any inefficiencies due to deadtime or due to individual problems with a given subdetector that prevent the ATLAS data taking to proceed (4.4%).
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/recEffByWeek.png
eps file
ATLAS Warm Start
When the stable beam flag is raised, some of the tracking and muon detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. Shown is the time this procedure took after declaring stable beams. The typical time is 5-10’. The occasional spikes are due to either caution e.g. when the background conditions have changed or due to DAQ problems during this procedure that prevented ATLAS going into this “READY” mode.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/readyTimeByFill.png
eps file
Number of Interactions per Crossing
The maximum mean number of events per beam crossing versus day. The mean number of events per crossing is calculated from the per bunch luminosity assuming a total inelastic cross section of 71.5 mb. The online luminosity measurement is used for this calculation as for the luminosity plots. Only the maximum value during stable beam periods is shown.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakMuByDay.png
eps file

Luminosity Summary Information for Pb-Pb (Heavy Ion) Collisions

Total Integrated Luminosity
Cumulative integrated luminosity versus day delivered to (dark blue), and recorded by ATLAS (light blue) for Heavy Ion (Pb) collisions during stable beams and for 2.76 TeV centre-of-mass energy per nucleon. The delivered luminosity accounts for the luminosity delivered from the start of stable beams until the LHC requests ATLAS to turn the sensitive detector off to allow a beam dump or beam studies. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total Pb-Pb nuclear cross section of 7.65 barn. The detection efficiency of 79%, for the current method used, is obtained from Monte Carlo simulation.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/HI/figs/sumLumiByDay.png
eps file
Integrated Luminosity per day
Same as above but not cumulative.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/HI/figs/lumiByDay.png
eps file
Peak Luminosity per day
The maximum instantaneous luminosity versus day delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/HI/figs/peakLumiByDay.png
eps file

Data Quality

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 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 partially be recovered when the data are reprocessed. The inefficiency in the Tile calorimeter arises from an incorrect masking of a channel in a single run which will be fixed for future reprocessings. The inefficiency in the CSC is due to 6/16 problematic chambers on one side of the detector during a 3-day period.

The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B, LBSUMM#DetStatus-pass1-analysis-2010X (X=C-I) for periods C-I.

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

Luminosity Plots for Specific LHC Fills

Line: 207 to 289
 
Deleted:
<
<

Data Quality

 
Deleted:
<
<
Luminosity weighted relative fraction of detector uptime and good quality data delivery of the various ATLAS subsystems during LHC fills with stable beams at √s=7 TeV between March 30th and August 30th, corresponding to an integrated luminosity of 3.6 pb-1 recorded by ATLAS during stable LHC beams. Not included in the numbers is the 1.5% average DAQ inefficiency during runs with stable beams. Also not included are 36 nb-1 that were used for special detector commissioning studies and are not used for physics analyses.

When the stable beam flag is raised, the inner detector and muon systems undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. This procedure accounts for most of the inefficiencies seen in the inner tracking and muon systems. Inefficiencies in the electromagnetic and hadronic parts of the LAr calorimeter are due to isolated HV trips and noise bursts.

The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B, LBSUMM#DetStatus-pass1-analysis-2010C for period C, LBSUMM#DetStatus-v03-pass1-analysis-2010D-RPCloose for period D (D1–D6) and LBSUMM#DetStatus-v03-pass1-analysis-2010E for period E and LBSUMM#DetStatus-v03-pass1-analysis-2010F for period F.

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

Revision 392010-10-12 - EmmerichKneringer

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 52 to 52
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByDay.png
eps file
Changed:
<
<
logarithmic y-scale version
logarithmic y-scale version eps file
>
>
logarithmic y-scale version
logarithmic y-scale version eps file
 
Line: 87 to 87
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByWeek.png
eps file
Changed:
<
<
logarithmic y-scale version
logarithmic y-scale version eps file
>
>
logarithmic y-scale version
logarithmic y-scale version eps file
 

Revision 382010-09-18 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 23 to 23
 

Luminosity Summary Information

Added:
>
>

Versus day

 
Total Integrated Luminosity
Line: 55 to 56
 logarithmic y-scale version eps file
Changed:
<
<
<!--
>
>

Versus week

Total Integrated Luminosity
Cumulative luminosity versus week delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
 
Changed:
<
<
Total Number of Collision Events Observed
Cumulative number of events per day triggered by the Minimum Bias Trigger Scintillators (MBTS) before applying prescales for 7 TeV collision data and during LHC stable beam periods. The Level-1 MBTS trigger requires at least one hit on either side of ATLAS (A and C). The efficiency of the trigger for inelastic events is 80% (it is > 98% for non-diffractive events), obtained from Monte Carlo simulation. The contamination of the trigger from beam background is typically less than 1%, depending on the run conditions.
>
>
Integrated Luminosity per week
Integrated luminosity versus week delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumEventsByDay.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale eps file
 
Changed:
<
<
Collision Events Observed per day
Number of events per day triggered by the Minimum Bias Trigger Scintillators (MBTS) before applying prescales for 7 TeV collision data and during LHC stable beam periods. The Level-1 MBTS trigger requires at least one hit on each side of ATLAS (A and C). The efficiency of the trigger for inelastic events is 80% (it is > 98% for non-diffractive events), obtained from Monte Carlo simulation. The contamination of the trigger from beam background is typically less than 1%, depending on the run conditions.
>
>
Peak Luminosity per week
The maximum instantaneous luminosity versus week delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/eventsByDay.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByWeek.png
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
 
Deleted:
<
<
-->
 

Luminosity Plots for Specific LHC Fills

Revision 372010-09-17 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 194 to 194
 
Changed:
<
<
Luminosity weighted relative fraction of detector uptime and good quality data delivery of the various ATLAS subsystems during LHC fills with stable beams at sqrt(s)=7 TeV between March 30th and August 14th, corresponding to an integrated luminosity of 1.13 pb-1 recorded by ATLAS during stable LHC beams. Not included in the numbers is the 2.5% average DAQ inefficiency during runs with stable beams. Also not included are 36 nb-1 that were used for special detector commissioning studies and are not used for physics analyses.

When the stable beam flag is raised, the inner detector and muon systems undergo a so-called "warm start", which includes a ramp of the high voltage and, for the pixel system, turning on the preamplifiers. This procedure accounts for most of the inefficiencies seen in the inner tracking and muon systems. Inefficiencies in the electromagnetic and hadronic parts of the LAr calorimeter are due to isolated HV trips and noise bursts.

>
>
Luminosity weighted relative fraction of detector uptime and good quality data delivery of the various ATLAS subsystems during LHC fills with stable beams at √s=7 TeV between March 30th and August 30th, corresponding to an integrated luminosity of 3.6 pb-1 recorded by ATLAS during stable LHC beams. Not included in the numbers is the 1.5% average DAQ inefficiency during runs with stable beams. Also not included are 36 nb-1 that were used for special detector commissioning studies and are not used for physics analyses.
 
Added:
>
>
When the stable beam flag is raised, the inner detector and muon systems undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. This procedure accounts for most of the inefficiencies seen in the inner tracking and muon systems. Inefficiencies in the electromagnetic and hadronic parts of the LAr calorimeter are due to isolated HV trips and noise bursts.
 

Changed:
<
<
The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B and LBSUMM#DetStatus-pass1-analysis-2010C for period C, LBSUMM#DetStatus‐v03‐pass1‐analysis‐2010D‐RPCloose for period D (D1–D6) and LBSUMM#DetStatus‐v03‐pass1‐analysis‐2010E for period E (E1‐E5)
>
>
The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B, LBSUMM#DetStatus-pass1-analysis-2010C for period C, LBSUMM#DetStatus-v03-pass1-analysis-2010D-RPCloose for period D (D1–D6) and LBSUMM#DetStatus-v03-pass1-analysis-2010E for period E and LBSUMM#DetStatus-v03-pass1-analysis-2010F for period F.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoE5-v0.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoF-v0.png
 

Revision 362010-08-31 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 29 to 29
 Cumulative luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByDay.png
Changed:
<
<
eps file
>
>
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
 
Line: 37 to 39
 Integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByDay.png
Changed:
<
<
eps file
>
>
eps file
logarithmic y-scale version
logarithmic y-scale eps file
 
Line: 46 to 50
 The maximum instantaneous luminosity versus day delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByDay.png
Changed:
<
<
eps file
>
>
eps file
logarithmic y-scale version
logarithmic y-scale version eps file
 
<!--

Revision 352010-08-24 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 78 to 78
 

The luminosity values shown have been calibrated with van-der-Meer beam-separation scan data. The error on the luminosity is estimated to be 11%, dominated by the uncertainty in the beam intensities.

Added:
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1298.png eps file
 https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1225.png eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1121.png

Revision 342010-08-20 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 186 to 186
 
Added:
>
>
Luminosity weighted relative fraction of detector uptime and good quality data delivery of the various ATLAS subsystems during LHC fills with stable beams at sqrt(s)=7 TeV between March 30th and August 14th, corresponding to an integrated luminosity of 1.13 pb-1 recorded by ATLAS during stable LHC beams. Not included in the numbers is the 2.5% average DAQ inefficiency during runs with stable beams. Also not included are 36 nb-1 that were used for special detector commissioning studies and are not used for physics analyses.

When the stable beam flag is raised, the inner detector and muon systems undergo a so-called "warm start", which includes a ramp of the high voltage and, for the pixel system, turning on the preamplifiers. This procedure accounts for most of the inefficiencies seen in the inner tracking and muon systems. Inefficiencies in the electromagnetic and hadronic parts of the LAr calorimeter are due to isolated HV trips and noise bursts.

 
Deleted:
<
<
Luminosity weighted relative fraction of detector uptime and good quality data delivery of the various ATLAS subsystems during LHC fills with stable beams at √s=7 TeV between March 30th and July 19th, corresponding to an integrated luminosity of 346 nb−1 recorded by ATLAS. Not included in the numbers is the 1.8% average DAQ inefficiency during runs with stable beams.
 

Changed:
<
<
When the stable beam flag is raised, the inner detector and muon systems undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. This procedure accounts for most of the inefficiencies seen in the inner tracking and muon systems. Inefficiencies in the electromagnetic and hadronic parts of the LAr calorimeter are due to isolated HV trips and noise bursts.

The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B and LBSUMM#DetStatus-pass1-analysis-2010C for period C and LBSUMM#DetStatus-pass1-analysis-2010D-RPCloose for period D

>
>
The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B and LBSUMM#DetStatus-pass1-analysis-2010C for period C, LBSUMM#DetStatus‐v03‐pass1‐analysis‐2010D‐RPCloose for period D (D1–D6) and LBSUMM#DetStatus‐v03‐pass1‐analysis‐2010E for period E (E1‐E5)
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoD-v1.pdf
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoE5-v0.png
 

Revision 332010-08-18 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 102 to 102
 eps file
Added:
>
>
Specific Luminosity per BCID
Distribution of the specific luminosity recorded by ATLAS at 7 TeV for different LHC bunches (BCID), averaged over LHC fill 1256. The specific luminosity is defined as the luminosity per bunch and per unit bunch charge, and is inversely proportional to the product of the horizontal and vertical convolved beam sizes at the IP. Due to the fill pattern, of the 25 bunches in each ring, only 16 are colliding in IP1; the background from the bunches that do not collide in ATLAS remains invisible on a linear scale, since it lies almost four orders of magnitude below the actual luminosity. The maximum bunch-to-bunch spread in specific luminosity approaches 40%, implying a variation of almost a factor of 2 in the product of the horizontal and vertical emittances of colliding-bunch pairs.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/fill1256_bcidspec.png
Luminosity per BCID
Time evolution of the bunch-by-bunch instantaneous luminosity recorded by ATLAS at 7 TeV during LHC fill 1257. In this fill there were 16 bunch pairs colliding at the ATLAS interaction point IP1. The difference, at a given time, between the highest- and the lowest-luminosity bunch is a factor of about 1.6, reflecting the variation of bunch currents and emittances along the colliding-bunch trains.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/fill1257_bcthlum.png
 

Revision 322010-08-13 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 103 to 103
 
Added:
>
>

Comparisons of Different Methods Measuring the Luminosity

 
Changed:
<
<
ATLAS instantaneous luminosity
>
>
ATLAS instantaneous luminosity comparing LAr, MBTS and LUCID
 The ATLAS instantaneous luminosity as determined with the LAr (blue open circles), the LUCID (open squares), and MBTS (red triangles) sub-detectors (ATLAS run 152409). The two plots give the instantaneous luminosity with two different y-scale ranges.

Revision 312010-08-12 - unknown

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 135 to 135
 
Measurement of Rate of Events with at least one Track and corresponding Luminosity
Changed:
<
<
The plots show the event rate and instantaneous luminosity derived from counting events with at least one charged particle. The first plot shows the rate of events with at least one track with a pT > 500 MeV in the dashed blue histogram and the rate after corrections for event loss due to tracking, vertex and trigger efficiencies (approximately 4%) is shown by the black points. The systematic and statistical errors are shown by the green band. The second plot shows the instantaneous luminosity derived from the charged particle rate. Pythia 6 MC09 is used to correct the rate for acceptance effects. The systematic uncertainties are indicated by the green hashed band which include the track to charged particle correction uncertainties and the monte carlo acceptance correction. The later is the dominant source of uncertainty and is determined by comparing the acceptance corrections from Pythia 6 MC09 and Phojet. The last plot shows the instantaneous luminosity derived from the charged particle event counting to the Van der Meer calibrated Atlas luminosity measurement.
>
>
First Plot: Rate of events in LHC Fill 1005 with at least one charged primary particle with pT>0.5 GeV/c, |eta|<0.8, versus UTC time (solid markers). Also shown is the raw rate of events with at least one track in this acceptance range (dashed line). The correction factor applied to the raw rate to obtain the charged particle rate is 1.04 +\- 0.017. Error bars represent the statistical uncertainty, the colored bands include both the systematic and statistical uncertainties.

Second Plot: The instantaneous luminosity derived from counting of events with at least one charged primary particle (pT>0.5 GeV/c, |eta|<0.8) for LHC Fill 1005 as a function of UTC time. Pythia MC09 was used for the acceptance and cross-section models after the correction for tracking, vertex and trigger efficiencies. Error bars represent the statistical uncertainty, the colored bands include both the systematic and statistical uncertainties. The systematic uncertainties account for the correction procedure and the dependence on the Monte Carlo models used for the acceptance and cross-sections by comparing the results obtained with Pythia MC09 and Phojet.

Third Plot: The instantaneous luminosity derived from counting of events with at least one charged primary particle (pT>0.5 GeV/c, |eta|<0.8) for LHC Fill 1005 as a function of UTC time (black points) compared with the Van der Meer calibrated ATLAS luminosity measurement (blue triangles). Pythia MC09 was used for the acceptance and cross-section models for the charged particle analysis. Error bars represent the statistical uncertainty, the colored bands include both the systematic and statistical uncertainties. The systematic uncertainties on the charged particle method account for the correction procedure and the dependence on the Monte Carlo models used for the acceptance and cross-sections by comparing the results obtained with Pythia MC09 and Phojet.

 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/TrackRate.152166.png
eps file

Revision 302010-08-12 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 134 to 134
 
Changed:
<
<
ATLAS instantaneous luminosity
>
>
Measurement of Rate of Events with at least one Track and corresponding Luminosity
 The plots show the event rate and instantaneous luminosity derived from counting events with at least one charged particle. The first plot shows the rate of events with at least one track with a pT > 500 MeV in the dashed blue histogram and the rate after corrections for event loss due to tracking, vertex and trigger efficiencies (approximately 4%) is shown by the black points. The systematic and statistical errors are shown by the green band. The second plot shows the instantaneous luminosity derived from the charged particle rate. Pythia 6 MC09 is used to correct the rate for acceptance effects. The systematic uncertainties are indicated by the green hashed band which include the track to charged particle correction uncertainties and the monte carlo acceptance correction. The later is the dominant source of uncertainty and is determined by comparing the acceptance corrections from Pythia 6 MC09 and Phojet. The last plot shows the instantaneous luminosity derived from the charged particle event counting to the Van der Meer calibrated Atlas luminosity measurement.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/TrackRate.152166.png

Revision 292010-08-12 - unknown

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 135 to 135
 
ATLAS instantaneous luminosity
Changed:
<
<
The plots show (with two different y-scale ranges) the performance of the LAr (open circles) and LUCID zero counting OR (solid triangles) normalized to give the same integrated luminosity as the MBTS results. The MBTS (shaded area) result provides the ATLAS luminosity (ATLAS run 152409). The LAr instantaneous luminosity is corrected for the dead time in the data acquisition system, and therefore is an estimate of the LHC delivered luminosity at the ATLAS interaction point. Both the MBTS and the LUCID methods are not affected by data acquisition dead time. The corresponding cross section used to normalize the measurements is 71.5 mb includes non-diffractive, single-diffractive, and double-diffractive. The systematic uncertainty is dominated by model dependence in the diffractive components of the cross section. An indication of the size of this uncertainty is obtained by comparing PYHTIA and PHOJET which translates into a variation in the luminosity of about 15%. The uncertainty is 100% correlated between methods. The uncorrelated method-dependent systematic uncertainties are of order 5% for LAr, LUCID, and MBTS. The three curves show only the statistical error as the systematic uncertainties are time independent and largely correlated among the different methods. The statistical errors on the plots are not clearly visible as they are small compared to the size of the marker.
>
>
The plots show the event rate and instantaneous luminosity derived from counting events with at least one charged particle. The first plot shows the rate of events with at least one track with a pT > 500 MeV in the dashed blue histogram and the rate after corrections for event loss due to tracking, vertex and trigger efficiencies (approximately 4%) is shown by the black points. The systematic and statistical errors are shown by the green band. The second plot shows the instantaneous luminosity derived from the charged particle rate. Pythia 6 MC09 is used to correct the rate for acceptance effects. The systematic uncertainties are indicated by the green hashed band which include the track to charged particle correction uncertainties and the monte carlo acceptance correction. The later is the dominant source of uncertainty and is determined by comparing the acceptance corrections from Pythia 6 MC09 and Phojet. The last plot shows the instantaneous luminosity derived from the charged particle event counting to the Van der Meer calibrated Atlas luminosity measurement.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/run152409_relative_luminosity_0.png
eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/run152409_relative_luminosity.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/TrackRate.152166.png
eps file

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/TrackLumi.152166.png
eps file

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/Track/TrackLumivsLarLumi.152166_wVdM.png
eps file

 

Revision 282010-08-12 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 170 to 170
 
Changed:
<
<
Luminosity weighted relative fraction of detector uptime and good quality data delivery of the various ATLAS subsystems during LHC fills with stable beams at √s=7 TeV between March 30th and July 16th, corresponding to an integrated luminosity of 243 nb−1 recorded by ATLAS. Not included in the numbers is the 3.1% average DAQ inefficiency during runs with stable beams.
>
>
Luminosity weighted relative fraction of detector uptime and good quality data delivery of the various ATLAS subsystems during LHC fills with stable beams at √s=7 TeV between March 30th and July 19th, corresponding to an integrated luminosity of 346 nb−1 recorded by ATLAS. Not included in the numbers is the 1.8% average DAQ inefficiency during runs with stable beams.
 

When the stable beam flag is raised, the inner detector and muon systems undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. This procedure accounts for most of the inefficiencies seen in the inner tracking and muon systems. Inefficiencies in the electromagnetic and hadronic parts of the LAr calorimeter are due to isolated HV trips and noise bursts.

The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B and LBSUMM#DetStatus-pass1-analysis-2010C for period C and LBSUMM#DetStatus-pass1-analysis-2010D-RPCloose for period D

Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoD-v0.pdf
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoD-v1.pdf
 

Revision 272010-07-22 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 169 to 169
 
Changed:
<
<
Luminosity weighted relative fraction of detector uptime and good quality data delivery of the various ATLAS subsystems during LHC fills with stable beams at √s=7 TeV between March 30th and June 5th, corresponding to an integrated luminosity of 16.8 nb−1 recorded by ATLAS. Not included in the numbers is the 3.4% average DAQ inefficiency during runs with stable beams.
>
>
Luminosity weighted relative fraction of detector uptime and good quality data delivery of the various ATLAS subsystems during LHC fills with stable beams at √s=7 TeV between March 30th and July 16th, corresponding to an integrated luminosity of 243 nb−1 recorded by ATLAS. Not included in the numbers is the 3.1% average DAQ inefficiency during runs with stable beams.
 

Changed:
<
<
When the stable beam flag is raised, the inner detector and muon systems undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. This procedure accounts for most of the inefficiencies seen in the inner tracking and muon systems. The inefficiencies in the electromagnetic and hadronic parts of the LAr calorimeter are primarily due to test runs, where the high voltage was lowered deliberately, and due to occasional HV trips.
>
>
When the stable beam flag is raised, the inner detector and muon systems undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. This procedure accounts for most of the inefficiencies seen in the inner tracking and muon systems. Inefficiencies in the electromagnetic and hadronic parts of the LAr calorimeter are due to isolated HV trips and noise bursts.
 

Changed:
<
<
The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B and LBSUMM#DetStatus-pass1-analysis-2010C for period C
>
>
The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B and LBSUMM#DetStatus-pass1-analysis-2010C for period C and LBSUMM#DetStatus-pass1-analysis-2010D-RPCloose for period D
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoC-v0.pdf
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoD-v0.pdf
 

Revision 262010-07-21 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 20 to 20
 

Conference Notes

Added:
>
>
 

Luminosity Summary Information

Revision 252010-07-16 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 71 to 71
 

Luminosity Plots for Specific LHC Fills

Changed:
<
<
ATLAS instantaneous luminosity
>
>
ATLAS instantaneous luminosity
 ATLAS instantaneous luminosity profiles as measured online for representative LHC fills with 7 TeV centre-of-mass energy in 2010. The gray shaded curves give the delivered luminosity, the green shaded curves show the delivered luminosity during stable beam conditions allowing ATLAS to turn on their tracking devices, and the yellow shaded curves give the recorded luminosity with the entire detector available. The missing recording at around 10:00 during Fill 1104 was caused by an intermediate removal of the stable beams condition flag by the LHC.

Deleted:
<
<
The bottom plot depicts the luminosity profiles of four consecutive LHC fills between July 12 and 15, 2010.

 The luminosity values shown have been calibrated with van-der-Meer beam-separation scan data. The error on the luminosity is estimated to be 11%, dominated by the uncertainty in the beam intensities.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1225.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1121.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1225.png eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1121.png
 eps file
Changed:
<
<

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1104.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1104.png
 eps file
Changed:
<
<

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1058.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1058.png eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png
 eps file

Revision 242010-07-16 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 68 to 68
 
-->
Changed:
<
<

Luminosity Plots for Specific Runs

>
>

Luminosity Plots for Specific LHC Fills

 
ATLAS instantaneous luminosity
Changed:
<
<
The ATLAS instantaneous luminosity as measured online for LHC fills 1005 on March 30th and 1058 on April 24th. Shown are the delivered luminosity, the luminosity with stable beams and the recorded luminosity. Fill 1005 was the first fill where 7 TeV collisions were achieved. Fill 1058 was the first fill where 7 TeV collisions were achieved with beta*=2m.
>
>
ATLAS instantaneous luminosity profiles as measured online for representative LHC fills with 7 TeV centre-of-mass energy in 2010. The gray shaded curves give the delivered luminosity, the green shaded curves show the delivered luminosity during stable beam conditions allowing ATLAS to turn on their tracking devices, and the yellow shaded curves give the recorded luminosity with the entire detector available. The missing recording at around 10:00 during Fill 1104 was caused by an intermediate removal of the stable beams condition flag by the LHC.

The bottom plot depicts the luminosity profiles of four consecutive LHC fills between July 12 and 15, 2010.

The luminosity values shown have been calibrated with van-der-Meer beam-separation scan data. The error on the luminosity is estimated to be 11%, dominated by the uncertainty in the beam intensities.

 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1225.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1121.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1104.png
eps file
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1058.png
Changed:
<
<
eps file
>
>
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png
eps file
 

ATLAS instantaneous luminosity
Changed:
<
<
ATLAS instantaneous luminosity profiles as measured online for three LHC fills, 1104, 1121 and 1122, taken respectively on May 15/16, 24 and 25, 2010. The gray shaded curves give the delivered luminosity, the green shaded curves show the delivered luminosity during stable beam conditions allowing ATLAS to turn on their tracking devices, and the yellow shaded curves give the recorded luminosity with the entire detector available. The missing recording at around 10:00 during Fill 1104 was caused by an intermediate removal of the stable beams condition flag by the LHC.
>
>
ATLAS instantaneous luminosity profiles as measured online during four consecutive LHC fills with 7 TeV centre-of-mass energy and stable beams between July 12 and 15, 2010. The gray shaded curves give the delivered luminosity, the green shaded curves show the delivered luminosity during stable beam conditions allowing ATLAS to turn on their tracking devices, and the yellow shaded curves give the recorded luminosity with the entire detector available.

The total time of stable beams during these fills is 41.8 hours. The total delivered (recorded) luminosity is 142.5 nb−1 (138.9 nb−1). The luminosity values given have been calibrated with van-der-Meer beam-separation scan data. The error on the luminosity is estimated to be 11%, dominated by the uncertainty in the beam intensities.

 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1104.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1121.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1122.png
eps file
>
>
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumiJuly12-15.png
eps file
 

Revision 232010-07-07 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 27 to 27
 
Total Integrated Luminosity
Cumulative luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByDayVdM.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByDay.png
eps file
 
Integrated Luminosity per day
Integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByDayVdM.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByDay.png
eps file
 
Line: 44 to 44
 
Peak Luminosity per day
The maximum instantaneous luminosity versus day delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByDayVdM.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByDay.png
eps file
 
<!--

Revision 222010-07-07 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 25 to 25
 
Total Integrated Luminosity
Changed:
<
<
Cumulative integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total inelastic cross section of 71.5 mb. There is a large overall uncertainty on the luminosity due to uncertainties in the inelastic cross section and in the individual contributions from non-diffractive, single-diffractive and double-diffractive events. ATLAS has a large variety of algorithms to determine the luminosity. The choice of algorithm gets adjusted on a regular basis to optimize the reliability trading e.g. the sensitivity to backgrounds, the statistical uncertainty and the linearity. All algorithms agree so far within 10%.
>
>
Cumulative luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByDay.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByDayVdM.png
eps file
 
Integrated Luminosity per day
Changed:
<
<
Integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total inelastic cross section of 71.5 mb. There is a large overall uncertainty on the luminosity due to uncertainties in the inelastic cross section and in the individual contributions from non-diffractive, single-diffractive and double-diffractive events. ATLAS has a large variety of algorithms to determine the luminosity. The choice of algorithm gets adjusted on a regular basis to optimize the reliability trading e.g. the sensitivity to backgrounds, the statistical uncertainty and the linearity. All algorithms agree so far within 10%.
>
>
Integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function [ref to CONF note when released]. The systematic uncertainty of the luminosity measurement is estimated to be 11%, dominated by the uncertainty in the beam current product of 10%.
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByDay.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByDayVdM.png
eps file
 
Line: 44 to 44
 
Peak Luminosity per day
The maximum instantaneous luminosity versus day delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByDay.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByDayVdM.png
eps file
 
<!--

Revision 212010-06-29 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 159 to 159
 
Added:
>
>

Data Quality

Luminosity weighted relative fraction of detector uptime and good quality data delivery of the various ATLAS subsystems during LHC fills with stable beams at √s=7 TeV between March 30th and June 5th, corresponding to an integrated luminosity of 16.8 nb−1 recorded by ATLAS. Not included in the numbers is the 3.4% average DAQ inefficiency during runs with stable beams.

When the stable beam flag is raised, the inner detector and muon systems undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. This procedure accounts for most of the inefficiencies seen in the inner tracking and muon systems. The inefficiencies in the electromagnetic and hadronic parts of the LAr calorimeter are primarily due to test runs, where the high voltage was lowered deliberately, and due to occasional HV trips.

The table corresponds to the DQ tag LBSUMM#DetStatus-v03-repro04-01 for periods A and B and LBSUMM#DetStatus-pass1-analysis-2010C for period C

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/DataQuality/atlas-on-and-dq-eff-periodAtoC-v0.pdf
 

Revision 202010-06-06 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 17 to 17
 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.
Added:
>
>

Conference Notes

 

Luminosity Summary Information

Revision 192010-06-03 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 44 to 44
 eps file
Added:
>
>
<!--
 
Total Number of Collision Events Observed
Cumulative number of events per day triggered by the Minimum Bias Trigger Scintillators (MBTS) before applying prescales for 7 TeV collision data and during LHC stable beam periods. The Level-1 MBTS trigger requires at least one hit on either side of ATLAS (A and C). The efficiency of the trigger for inelastic events is 80% (it is > 98% for non-diffractive events), obtained from Monte Carlo simulation. The contamination of the trigger from beam background is typically less than 1%, depending on the run conditions.
Line: 60 to 61
 eps file
Added:
>
>
-->
 

Luminosity Plots for Specific Runs

Revision 182010-06-02 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 45 to 45
 
Changed:
<
<
Total Collision Events Observed
>
>
Total Number of Collision Events Observed
 Cumulative number of events per day triggered by the Minimum Bias Trigger Scintillators (MBTS) before applying prescales for 7 TeV collision data and during LHC stable beam periods. The Level-1 MBTS trigger requires at least one hit on either side of ATLAS (A and C). The efficiency of the trigger for inelastic events is 80% (it is > 98% for non-diffractive events), obtained from Monte Carlo simulation. The contamination of the trigger from beam background is typically less than 1%, depending on the run conditions.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumEventsByDay.png

Revision 172010-06-02 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 21 to 21
 
Total Integrated Luminosity
Changed:
<
<
Cumulative integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total inelastic cross section of 71.5 mb. The detection efficiency of 65%, for the current method used, is obtained from Monte Carlo simulation. There is a large overall uncertainty on the luminosity due to uncertainties in the inelastic cross section and in the individual contributions from non-diffractive, single-diffractive and double-diffractive events.
>
>
Cumulative integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total inelastic cross section of 71.5 mb. There is a large overall uncertainty on the luminosity due to uncertainties in the inelastic cross section and in the individual contributions from non-diffractive, single-diffractive and double-diffractive events. ATLAS has a large variety of algorithms to determine the luminosity. The choice of algorithm gets adjusted on a regular basis to optimize the reliability trading e.g. the sensitivity to backgrounds, the statistical uncertainty and the linearity. All algorithms agree so far within 10%.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByDay.png
eps file
Line: 29 to 29
 
Integrated Luminosity per day
Changed:
<
<
Integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total inelastic cross section of 71.5 mb. The detection efficiency of 65%, for the current method used, is obtained from Monte Carlo simulation. There is a large overall uncertainty on the luminosity due to uncertainties in the inelastic cross section and in the individual contributions from non-diffractive, single-diffractive and double-diffractive events.
>
>
Integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total inelastic cross section of 71.5 mb. There is a large overall uncertainty on the luminosity due to uncertainties in the inelastic cross section and in the individual contributions from non-diffractive, single-diffractive and double-diffractive events. ATLAS has a large variety of algorithms to determine the luminosity. The choice of algorithm gets adjusted on a regular basis to optimize the reliability trading e.g. the sensitivity to backgrounds, the statistical uncertainty and the linearity. All algorithms agree so far within 10%.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByDay.png
eps file

Revision 162010-06-02 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 67 to 67
 
ATLAS instantaneous luminosity
The ATLAS instantaneous luminosity as measured online for LHC fills 1005 on March 30th and 1058 on April 24th.
Changed:
<
<
Shown are the delivered luminosity, the luminosity with stable beams and the recorded luminosity. Fill 1005 was the first fill where 7 TeV collisions were achieved. Fill 1058 was the first fill where 7 TeV collisions were achieved with beta*=2m.
>
>
Shown are the delivered luminosity, the luminosity with stable beams and the recorded luminosity. Fill 1005 was the first fill where 7 TeV collisions were achieved. Fill 1058 was the first fill where 7 TeV collisions were achieved with beta*=2m.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png
eps file

Revision 152010-06-02 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 69 to 69
 The ATLAS instantaneous luminosity as measured online for LHC fills 1005 on March 30th and 1058 on April 24th. Shown are the delivered luminosity, the luminosity with stable beams and the recorded luminosity. Fill 1005 was the first fill where 7 TeV collisions were achieved. Fill 1058 was the first fill where 7 TeV collisions were achieved with beta*=2m.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png
 eps file
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1058.png
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1058.png
 eps file
Added:
>
>

ATLAS instantaneous luminosity
ATLAS instantaneous luminosity profiles as measured online for three LHC fills, 1104, 1121 and 1122, taken respectively on May 15/16, 24 and 25, 2010. The gray shaded curves give the delivered luminosity, the green shaded curves show the delivered luminosity during stable beam conditions allowing ATLAS to turn on their tracking devices, and the yellow shaded curves give the recorded luminosity with the entire detector available. The missing recording at around 10:00 during Fill 1104 was caused by an intermediate removal of the stable beams condition flag by the LHC.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1104.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1121.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1122.png
eps file
 
ATLAS instantaneous luminosity
The ATLAS instantaneous luminosity as determined with the LAr (blue open circles), the LUCID (open squares), and MBTS (red triangles) sub-detectors (ATLAS run 152409). The two plots give the

Revision 142010-06-01 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 54 to 54
 
Collision Events Observed per day
Changed:
<
<
Number of events per day triggered by the Minimum Bias Trigger Scintillators (MBTS) before applying prescales for 7 TeV collision data and during LHC stable beam periods. The Level-1 MBTS trigger requires at least one hit on either side of ATLAS (A and C). The efficiency of the trigger for inelastic events is 80% (it is > 98% for non-diffractive events), obtained from Monte Carlo simulation. The contamination of the trigger from beam background is typically less than 1%, depending on the run conditions.
>
>
Number of events per day triggered by the Minimum Bias Trigger Scintillators (MBTS) before applying prescales for 7 TeV collision data and during LHC stable beam periods. The Level-1 MBTS trigger requires at least one hit on each side of ATLAS (A and C). The efficiency of the trigger for inelastic events is 80% (it is > 98% for non-diffractive events), obtained from Monte Carlo simulation. The contamination of the trigger from beam background is typically less than 1%, depending on the run conditions.
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/eventsByDay.png
eps file

Revision 132010-05-23 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 69 to 69
 The ATLAS instantaneous luminosity as measured online for LHC fills 1005 on March 30th and 1058 on April 24th. Shown are the delivered luminosity, the luminosity with stable beams and the recorded luminosity. Fill 1005 was the first fill where 7 TeV collisions were achieved. Fill 1058 was the first fill where 7 TeV collisions were achieved with beta*=2m.
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png
eps file
 
Changed:
<
<
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1058.png
eps file
>
>
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1058.png
eps file
 
ATLAS instantaneous luminosity

Revision 122010-05-22 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 66 to 66
 
ATLAS instantaneous luminosity
Added:
>
>
The ATLAS instantaneous luminosity as measured online for LHC fills 1005 on March 30th and 1058 on April 24th. Shown are the delivered luminosity, the luminosity with stable beams and the recorded luminosity. Fill 1005 was the first fill where 7 TeV collisions were achieved. Fill 1058 was the first fill where 7 TeV collisions were achieved with beta*=2m.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1005.png
eps file
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/OperationalPlots/lumi1058.png
eps file
ATLAS instantaneous luminosity
 The ATLAS instantaneous luminosity as determined with the LAr (blue open circles), the LUCID (open squares), and MBTS (red triangles) sub-detectors (ATLAS run 152409). The two plots give the instantaneous luminosity with two different y-scale ranges.

Revision 112010-05-10 - PatrickJussel

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
<!--  
  • Set DENYTOPICVIEW =
Added:
>
>
  • Set ALLOWTOPICCHANGE = atlas-readaccess-current-physicists
 
-->
Added:
>
>
 

Luminosity and Run Statistics Plots for 2010 Beam Data

<!--optional-->

Revision 102010-05-07 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 71 to 71
  and therefore is an estimate of the LHC delivered luminosity at the ATLAS interaction point. Both the MBTS and the LUCID methods are not affected by data acquisition dead time. For each of these measurements the acceptance is independently calculated using the PYTHIA
Changed:
<
<
Monte Carlo simulation of the $pp$ inelastic interactions.
>
>
Monte Carlo simulation of the proton-proton inelastic interactions.
 The corresponding cross section used to normalize the measurements is 71.5 mb and it includes non-diffractive, single-diffractive, and double-diffractive processes. The systematic uncertainty is dominated by model dependence in the diffractive components of the
Line: 83 to 83
 The statistical errors on the plots are not clearly visible as they are small compared to the size of the markers. For this run the estimated delivered luminosity is
Changed:
<
<
75.6 ± 15.1 μ b−1(stat+syst).
>
>
(75.6 ± 15.1) μ b−1(stat+syst).
 
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/run152409_absolute_luminosity_0.png
eps file

Revision 92010-05-07 - AndreaMessina

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 62 to 61
 

Luminosity Plots for Specific Runs

Deleted:
<
<
 
Changed:
<
<
Title
Legend...
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/xxx.png
eps file
>
>

ATLAS instantaneous luminosity
The ATLAS instantaneous luminosity as determined with the LAr (blue open circles), the LUCID (open squares), and MBTS (red triangles) sub-detectors (ATLAS run 152409). The two plots give the instantaneous luminosity with two different y-scale ranges. The LAr instantaneous luminosity is corrected for the dead time in the data acquisition system, and therefore is an estimate of the LHC delivered luminosity at the ATLAS interaction point. Both the MBTS and the LUCID methods are not affected by data acquisition dead time. For each of these measurements the acceptance is independently calculated using the PYTHIA Monte Carlo simulation of the $pp$ inelastic interactions. The corresponding cross section used to normalize the measurements is 71.5 mb and it includes non-diffractive, single-diffractive, and double-diffractive processes. The systematic uncertainty is dominated by model dependence in the diffractive components of the cross section. An indication of the size of this uncertainty is obtained by comparing PYHTIA and PHOJET which translates into a variation in the luminosity of about 15%. The uncertainty is 100% correlated between methods. The uncorrelated method-dependent systematic uncertainties are of order 5% for LAr, LUCID, and MBTS. The curves show only the statistical error as the systematic uncertainty is time independent. The statistical errors on the plots are not clearly visible as they are small compared to the size of the markers. For this run the estimated delivered luminosity is 75.6 ± 15.1 μ b−1(stat+syst).
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/run152409_absolute_luminosity_0.png
eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/run152409_absolute_luminosity.png
eps file
ATLAS instantaneous luminosity
The plots show (with two different y-scale ranges) the performance of the LAr (open circles) and LUCID zero counting OR (solid triangles) normalized to give the same integrated luminosity as the MBTS results. The MBTS (shaded area) result provides the ATLAS luminosity (ATLAS run 152409). The LAr instantaneous luminosity is corrected for the dead time in the data acquisition system, and therefore is an estimate of the LHC delivered luminosity at the ATLAS interaction point. Both the MBTS and the LUCID methods are not affected by data acquisition dead time. The corresponding cross section used to normalize the measurements is 71.5 mb includes non-diffractive, single-diffractive, and double-diffractive. The systematic uncertainty is dominated by model dependence in the diffractive components of the cross section. An indication of the size of this uncertainty is obtained by comparing PYHTIA and PHOJET which translates into a variation in the luminosity of about 15%. The uncertainty is 100% correlated between methods. The uncorrelated method-dependent systematic uncertainties are of order 5% for LAr, LUCID, and MBTS. The three curves show only the statistical error as the systematic uncertainties are time independent and largely correlated among the different methods. The statistical errors on the plots are not clearly visible as they are small compared to the size of the marker.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/run152409_relative_luminosity_0.png
eps file https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/run152409_relative_luminosity.png
eps file
 

Revision 82010-05-06 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 61 to 61
 
Added:
>
>

Luminosity Plots for Specific Runs

Title
Legend...
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/2010/Luminosity/MBTS_LUCID_LAr/xxx.png
eps file
 
<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->
<!--***********************************************************-->

Revision 72010-05-06 - BeateHeinemann

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 15 to 15
 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.
Changed:
<
<

Luminosity

>
>

Luminosity Summary Information

 
Total Integrated Luminosity

Revision 62010-04-16 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 61 to 61
 
Deleted:
<
<

Beam spot (luminous region)

Title
Legend...
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/myplot.png
eps file
 
<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->
<!--***********************************************************-->

Revision 52010-04-15 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 61 to 61
 
Added:
>
>

Beam spot (luminous region)

Title
Legend...
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/myplot.png
eps file
 
<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->

Revision 42010-04-14 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 6 to 6
 
 
  • Set DENYTOPICVIEW =
-->
Changed:
<
<

Run Statistics and Luminosity Plots for 2010 Beam Data

>
>

Luminosity and Run Statistics Plots for 2010 Beam Data

 
<!--optional-->
Line: 18 to 18
 

Luminosity

Added:
>
>
Total Integrated Luminosity
Cumulative integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total inelastic cross section of 71.5 mb. The detection efficiency of 65%, for the current method used, is obtained from Monte Carlo simulation. There is a large overall uncertainty on the luminosity due to uncertainties in the inelastic cross section and in the individual contributions from non-diffractive, single-diffractive and double-diffractive events.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumLumiByDay.png
eps file
 
Changed:
<
<
Plots to come ....

http://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/dec2009/plot.png
>
>
Integrated Luminosity per day
Integrated luminosity versus day delivered to (green), and recorded by ATLAS (yellow) during stable beams and for 7 TeV centre-of-mass energy. Given is the luminosity as determined online using counting rates measured by the luminosity detectors, and by assuming a total inelastic cross section of 71.5 mb. The detection efficiency of 65%, for the current method used, is obtained from Monte Carlo simulation. There is a large overall uncertainty on the luminosity due to uncertainties in the inelastic cross section and in the individual contributions from non-diffractive, single-diffractive and double-diffractive events.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/lumiByDay.png
eps file
Peak Luminosity per day
The maximum instantaneous luminosity versus day delivered to ATLAS. The luminosity determination is the same as described above for the integrated luminosity. Only the peak luminosity during stable beam periods is shown.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/peakLumiByDay.png
eps file
 
Added:
>
>
Total Collision Events Observed
Cumulative number of events per day triggered by the Minimum Bias Trigger Scintillators (MBTS) before applying prescales for 7 TeV collision data and during LHC stable beam periods. The Level-1 MBTS trigger requires at least one hit on either side of ATLAS (A and C). The efficiency of the trigger for inelastic events is 80% (it is > 98% for non-diffractive events), obtained from Monte Carlo simulation. The contamination of the trigger from beam background is typically less than 1%, depending on the run conditions.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/sumEventsByDay.png
eps file
Collision Events Observed per day
Number of events per day triggered by the Minimum Bias Trigger Scintillators (MBTS) before applying prescales for 7 TeV collision data and during LHC stable beam periods. The Level-1 MBTS trigger requires at least one hit on either side of ATLAS (A and C). The efficiency of the trigger for inelastic events is 80% (it is > 98% for non-diffractive events), obtained from Monte Carlo simulation. The contamination of the trigger from beam background is typically less than 1%, depending on the run conditions.
https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DataSummary/figs/eventsByDay.png
eps file
 
Line: 36 to 70
 
<!--Please add the name of someone who is responsible for this page so that he/she can be contacted if changes are needed.
The creator's name will be added by default, but this can be replaced if appropriate.
Put the name first, without dashes.-->
Changed:
<
<
Responsible: Andreas Hoecker and Beate Heinemann
>
>
Responsible: Andreas Hoecker, Beate Heinemann and Eric Torrence
 
<!--Once this page has been reviewed, please add the name and the date e.g. StephenHaywood - 31 Oct 2006 -->
Last reviewed by: Never reviewed

Revision 32010-04-08 - AndreasHoecker

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 15 to 15
 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.
Changed:
<
<

Figures

>
>

Luminosity

 
Changed:
<
<
Cumulative luminosity ....
>
>
Plots to come ....
 
Changed:
<
<
http://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/dec2009/atlas_number_of_collision_events_2009.png
>
>
http://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/dec2009/plot.png
 
Changed:
<
<
-
>
>
 
<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->
<!--***********************************************************-->

Revision 22010-04-08 - AndreaMessina

Line: 1 to 1
 
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
Line: 26 to 26
 
Added:
>
>
-
 
<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->
<!--***********************************************************-->

Revision 12010-04-08 - AndreasHoecker

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="AtlasResults"
Warning
Can't INCLUDE Atlas.AtlasPublicTopic repeatedly, topic is already included.
<!--  
  • Set DENYTOPICVIEW =
-->

Run Statistics and Luminosity Plots for 2010 Beam Data

<!--optional-->

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.

Figures

Cumulative luminosity ....

http://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/dec2009/atlas_number_of_collision_events_2009.png
<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->
<!--***********************************************************-->


<!--Please add the name of someone who is responsible for this page so that he/she can be contacted if changes are needed.
The creator's name will be added by default, but this can be replaced if appropriate.
Put the name first, without dashes.-->
Responsible: Andreas Hoecker and Beate Heinemann
<!--Once this page has been reviewed, please add the name and the date e.g. StephenHaywood - 31 Oct 2006 -->
Last reviewed by: Never reviewed
 
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