Introduction
HGTDPyAna is an analysis framework used to reconstruct the HGTD test beam data recordered by the oscilloscopes.
It was used for HGTD test beam the
paper
.
The code can be found in the following
svn repository
and will be migrating to git soon.
The framework takes as inputs the raw oscilloscope data (the .dat files containing the actual data and .txt containing the metadata). The ouput is a root file containing a tree containing various variable for each event and each channels.
Ntuples
Where to find them?
The Ntuples can be found on eos at: YYYYY
The latest recommended version is:
XXXXX
What is the content?
The variables that can be found in the trees are:
Branch Name |
variable |
comments |
pulseHeight |
maximum of the pulse amplitude |
|
timeCFD |
time reconstruction with a Constant Fraction Discriminator |
was named timeCFD1 in previous versions |
timeCTD |
time reconstruction with a Constant Threshold Discriminator |
was named timeFTD in previous versions |
timeZCD |
time reconstruction with a Zero Crossing Discriminator |
was named timeCFD2 in previous versions |
timeAtMax |
time at wich the amplitude is maximal |
|
pedestal |
pedestal |
|
noise |
noise |
|
charge |
integral of the pulse divided by the transimpedance |
|
jitter |
N/(dV/dt) |
|
riseTime1090 |
RiseTime computed from 10% to 90% of the maximum amplitude |
|
Each branch is a vector containing an entry for each channel. More information on these variables can be found in the HGTD test beam (
paper
).
How to run the code?
Getting and setuping the code
#check out
svn co svn+ssh://svn.cern.ch/reps/atlasgroups/Detectors/LAr/HGTD/Oct16TB/Analysis/trunk Analysis
cd Analysis
#setup
source mysetup.sh
Options
option |
explanation |
--runNumber |
Run number |
--inputDir |
Input directory (not EOS!!!) |
--outputDir |
Output directory |
--maxEvent |
Nb of events analyzed |
--skipEvent |
Nb of events skipped |
--CTDThres |
Threshold for the CTD method in mV |
--CFDFrac |
CFD and ZCD fraction |
--ZCDDelay |
ZCD delay |
--drawPulse |
Draw the pulse for each pulse and each event |
--debug |
print more information |
--filename |
input filename |
--nChannels |
number of channels |
Usage (example)
#You can run on a subsample:
python python/ana.py --inputDir /afs/cern.ch/work/m/makovec/public/Data/TESTBEAM/ -r 1478044194 --maxEvent 1000
#You can also directly specify the filename instead of the inputdir and the run number
python python/ana.py -f /data/atlas/HGTD/TestBeam/June2017/data_1498858885.dat
#If a run is not added to one of the database files (Database/RunInfo*dat), you will have to specify the number of channels
python python/ana.py --debug -f /afs/cern.ch/work/m/makovec/public/Data/TESTBEAM/data_1478044194.dat --nChannels 4 --maxEvent 1000
python python/ana.py --debug -f /afs/cern.ch/work/m/makovec/public/Data/TESTBEAM/data_1498858885.dat --nChannels 3 --maxEvent 100
--
MakovecNikola - 2017-10-11