Data Quality (RunLog)
New page under construction!!!
Starting in 2008 the first level DQ is performed by the shift crew during data taking. A GUI in the control room collects the run list: http://www.hep.phy.cam.ac.uk/~gmavroma/calice/testbeam/RunList.dat with a series of information on the beam/DAQ/detectors quality. The meaning of the entries in the file is explained in the file header.
The value stored in the ascii file for the DQ bit is a 8bits word written (for convenience) in hexadecimal calculated as the following:
set dqBitsNewHex [ expr \ $dqIsTCatcher*pow(2,0) + $dqIsHCAL*pow(2,1) + $dqIsECAL*pow(2,2) + $dqIsChambers*pow(2,3) + $dqIsDAQ*pow(2,4) + $dqIsBeam*pow(2,5) + $dqIsBad*pow(2,6) + $dqIsOther*pow(2,7)]
The bit structure is
Other - Bad - Beam - DAQ - Chamb - ECAL - HCAL - !TailCatcher X X X X X X X X
where the bit X should be set (in principle) to one if the operator on shift finds something anomalous in the corresponding variable; e.g., if in a run only the DAQ was screwed up, then the bit sequence should appear as 0001 0000. In hexa this is translated in 0x10. In the notation 0xXY, the values X and Y translate in hexa the last
[Other - ... - Bad] and the first [Chamb - ... - TailCatcher] 4bit words.
The "Other" field refers to all the "bad" situations which can be encountered during data taking, and were somehow not considered as likely (or we haven't even thought about them at all when writing the program!).
Similarly, in case of bad (problem, out of readout, or for whatever reason) TailCatcher, we have 0x01; 0x04 for bad ECAL 0x04; 0x22 for bad Beam+HCAL, and so ....