Detector run quality flag
Detector run quality#
The QC shifter set the detector run quality based on instructions and discussion/feedback and approval from SL
-
For each run, each detector has a run quality for the entire run
-
At present the detector run quality apply to the entire run, time differential information under development. Therefore BAD to be selected only if the criteria apply to the entire run
-
By default, detector run quality is set to GOOD
-
Based on QC instructions and interaction with SL, the QC shifter set the detector run quality to BAD https://alice-qc-shifter.docs.cern.ch
-
The QC shifter should always add a bookkeeping entry per detector in bad run quality explaining the reason to mark the detector quality to BAD (tag detector and QC, title “Detector xx run quality to bad”)
-
In case the overall detector run quality is good but a time range of bad quality data during the data taking is identified, the QC shifter should add a dedicated bookkeeping entry with title “Detector xx run quality to good with bad time ranges” detailing the issues and concerned time period