AtlasPublicTopicHeader.png

Data Quality Information for Data

Introduction

Approved plots that can be shown by ATLAS speakers at conferences and similar events.
Please do not add figures on your own. Contact the Data Preparation Coordinators in case of questions and/or suggestions.

Data Quality

2018

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

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

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

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

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

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

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

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

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

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

2017

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

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

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

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

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

2016

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

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

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

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

2015

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

The table corresponds to the DQ tag DetStatus-v73-pro19-08 with lumi tag OflLumi-13TeV-003.

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/DQ-eff-table-2015-AugNov-2015.png
pdf file
LHCP Dataset: Luminosity weighted relative fraction of good quality data delivery by the various components of the ATLAS detector/trigger subsystems during LHC fills with stable beams in pp collisions at √s=13 TeV, and after switching the tracking detectors on. Runs between 3 June and 23 July 2015, corresponding to a recorded integrated luminosity of 173 pb-1, are shown. 
 
 An additional 22 pb-1 of data recorded in special conditions for detector calibration purposes is not shown. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency.

The table corresponds to the DQ tag DetStatus-v63-pro18 for data15_13TeV periods A,B, and C2-5 and DQ tag DetStatus-v64-pro19 for periods D3-6 with lumi tag OflLumi-13TeV-001.

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 tracking detectors on. Runs between 3 June and 16 July 2015, corresponding to a recorded integrated luminosity of 91 pb-1, are shown. 
 
 An additional 4 pb-1 of data recorded in special conditions for detector calibration purposes is not shown. When the stable beam flag is raised, the tracking detectors undergo a so-called "warm start", which includes a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The inefficiency due to this, as well as the DAQ inefficiency, are not included in the table above, but accounted for in the ATLAS data taking efficiency. The all good for physics efficiency includes additional requirements beyond the detector-related efficiencies shown here.

The table corresponds to the DQ tag DetStatus-v63-pro18 for data15_13TeV periods A,B, and C2-5 with lumi tag OflLumi-13TeV-001.

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

2013

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

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

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

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

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

2012

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

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

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

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 stablebeams in pp collisions at √s=8 TeV, and after switching the tracking detectors on. Runs between April 4th and September 17th, corresponding toa 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 stablebeams in pp collisions at √s=8 TeV, and after switching the tracking detectors on. Runs between April 4th and June 18th, corresponding toa recorded integrated luminosity of 6.3 fb-1, are accounted.

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

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

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

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

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

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

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

2011

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

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

This table reflects the data quality after the reprocessing.

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

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2011-AtoM-.png
Same DQ table but with the LAr components merged and AllGood efficiency as in the 2012 table

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

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

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

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

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

This table reflects the data quality after the reprocessing.

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

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

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

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

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

This table is for the Tier0 processing of this data.

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

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

https://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2011-AtoK-t0.png
NB The purpose of this table is to show the improvement in DQ we achieved from software improvements in the release 17 reprocessing. To be shown in conjunction with the table above!

Luminosity weighted relative fraction of good quality data delivery by the various ATLAS subsystems during LHC fills with stablebeams in pp collisions at √s=7 TeV, and after switching the tracking detectors on. Runs between March 13th and June 29th, corresponding toa 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://atlas.web.cern.ch/Atlas/GROUPS/DATAPREPARATION/PublicPlots/DQ/atlas-dq-eff-pp2011-BtoK-repro.png

2010

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

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

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

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


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

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng BtoH_DQ_repo.png r1 manage 36.3 K 2011-09-20 - 16:05 UnknownUser  
PNGpng BtoH_DQtier0.png r1 manage 44.5 K 2011-09-20 - 16:05 UnknownUser  
PNGpng atlas-dq-eff-2011-hi.png r1 manage 46.6 K 2012-02-07 - 13:25 UnknownUser  
PDFpdf atlas-dq-eff-periodBtoM-trigger-tableOnly.pdf r1 manage 136.2 K 2011-12-12 - 15:43 UnknownUser  
PNGpng atlas-dq-eff-pp2011-AtoK-repro.png r1 manage 48.0 K 2012-02-07 - 13:24 UnknownUser  
PNGpng atlas-dq-eff-pp2011-AtoK-t0.png r1 manage 56.2 K 2012-02-07 - 13:24 UnknownUser  
PNGpng atlas-dq-eff-pp2011-AtoM.png r1 manage 46.0 K 2012-02-07 - 13:23 UnknownUser  
PNGpng dqtable_2018_v1_1.png r1 manage 66.9 K 2018-06-04 - 15:23 UnknownUser  
Edit | Attach | Watch | Print version | History: r89 < r88 < r87 < r86 < r85 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r89 - 2018-11-12 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Atlas All webs login

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