There are two levels of data quality checks that are applied to testbeam data. The first level checks are done by the shift crew during data taking. Since 2008, information about special features of certain runs are not only documented in the eLog, but also in the graphical RunLog. A description of the data quality flags used in the RunLog can be found here.
The second level of data quality checks is performed on ROOT trees generated from the converted data "/grid/calice/tb-<site>/raw".
* <site> is either cern or fnal.
During the generation of these DQ-trees, the runs have to be reconstructed. The ROOT trees, the reconstructed files and tarballs comprising the Marlin steering files and different logfiles are stored on the grid. The grid folders are
/grid/calice/tb-<site>/data_quality/<version>/reco (reconstructed data)
<version> refers to common sets of code versions, steering parameters and database folders.
The different versions and their features are summarized in the following.
- uses calice_pro_test
DBFolder for Mip calibration (CERN): /cd_calice/Hcal/MIP/Approved/
DBFolder for Mip calibration (FNAL): /cd_calice/Hcal/MIP/test_av/
DBFolder for gain (CERN): /cd_calice/Hcal/Gain/Approved/
DBFolder for gain (FNAL): /test_nf/Hcal/Gain/ (separate average for May, July and September)
DBFolder for InterCalibration (CERN): /cd_calice/Hcal/Inter/Approved/
DBFolder for InterCalibration (FNAL): /test_nf/Hcal/Inter/ (separate average for May, July and September)
DQ Root Trees
The DQ root trees contain information of the main detector components of the calice test beam setup, therefore ECAL, HCAL, TCMT, Drift Chambers, Trigger and Slow control variables are stored in the trees. Several RootTreeWriter engines are used to transport the initial slcio collections to simple DQ tree variables.
A summary of the most important variables stored on the DQ-ROOT trees and the engines used to fill them can be found here:
Summary of DQ Engines
nHits_fix energySum_fix radius_fix
number of hits, total energy and radius. The prefix fix can be emc(ECAL), ahc(HCAL), tcm(TCMT)
cogX_fix, cogY_fix, cogZ_fix
cog for emc, ahc, tcm using all calorimeter layers (Energy weight)
cogI, cogJ, cogZ
Hcal cog in I,J coordinates using only first 5 calorimeter layers (Energy weight)
Hcal cog in I,J coordinates using only the first 5 calorimeter layers
hcal energy sum using only the first 5 calorimeter layers (Energy weight)
cogX5Layer, cogY5Layer, cogZ5Layer
cog of Hcal using only the first 5 calorimeter layers (Energy weight)
beamBit spillBit pedestalBit
beam, spill and pedestal trigger bits
pure pedestal, cosmic trigger bits
calibration (LED) trigger bit
Trigger bits for Cherenkow
a3x3Bit b3x3Bit a10x10Bit b10x10Bit
scintillator Trigger bits
scintillator Trigger bits
vetoBit multiBit multiADC
Veto, Multiparticle counter bit and ADC signal
x beam position on HCAL surface
y beam position on HCAL surface
x chi2 value
y chi2 value
Temperature of the 38 HCAL modules & 5 Sensors
Voltage of the 38*2 half module of HCAL
Current of the 38*2 half modules of HCAL
Stack X,Y and Theta position from AhcSroBlock
X,Y,Z Hcal stack position readed from DB Folder /cd_calice_cernbeam/Hcal/HcalDetectorPosition -available just for CERN data
The source code of the engines can be temporary found in "/nfs/flc/lc4/pool/vargas/caliceSoft/calice_dq/RootTreeWriter/doc/html/pages.html"
Analysing the DQ Root Trees
The analysis of the DQ-Root trees can be performed using the DQ_BaseClass. You can get the source code from the git repository: "/nfs/flc/lc4/pool/vargas/newDQCode"
A makefile is included, just type make and the executable ProcessDQTree will be created. Running this executable as:
- ./ProcessDQTree treeMyFavoriteRunNumber.root
will create a summaryDQtree.root file containing averaged variables of the run. Description of the filled variables can be found temporary on lc4, "file:///pool/vargas/newDQCode/documentation/html/index.html".