Labview
Number of packets
TODO
Chip occupancy
TODO
Raw chip data insight
TODO
EUDAQ
Runcontrol observables
TODO
AHCAL terminal output
TODO
Online display
TODO
Temperature
The temperature data is stored by the labview program to the TXT file. Example of the txt file:
The temperature of the temperature sensors T1-T6 are in Degrees of Celsius multiplied by 10 (stored number needs to be divided by 10 in order to obtain the temperature value), temperatures of DIF and POWER are directly in degrees of Celsius.
The txt file location is usually on the Frankenstein PC, for example in F:\CERN_2018_October\data.
The DQM PC (flchcallab6, 192.168.1.16) has scripts, that fetches the temperature files from the in the ~/TB2018/Temperature/ directory.
Setup of the scripts
Getting the plots
#in calice@flchcallab6:~/TB2018/Temperature$ ./script.sh
and wait for the output (script is slow).
AHCAL raw data analysis
Git repository https://github.com/jkvas/AHCAL-RAWutils has few programs, that can quickly process AHCAL (and BIF) raw files and extract some information:
- ahcalBifCorrelation: find of offsets, BIF vs SPIROC TDC correlation
- AhcalNoiseAnalysis: calculates a noise frequency with subtraction of trigger
- ahcalraw2txt: converts the raw file to the txt format, can output a histogram
- BIFStats: extracts timing information and statistics.
All programs provide help when executed with --help parameter
Noise
Noise can be extracted from the raw datausing the AhcalNoiseAnalysis program. Statistics can be even obtained from runs with the beam: triggered events can be removed from the statistics, but it won't work for events, that are not properly triggered (events outside the trigger scintillator beam area or 2 triggers close to each other).
Following script can analyze noise of all asics and channels:
following lines should be modified:
- line 8 (where is the analysis command)
- line 11 (list of port number as they are ordered in the testbeam)
- line 12 (run number range)
- line 14: where are the files located
- line 29: actual correlation shift (LDA offset)
It produces a big txt file with noise values in tab-separated format (example with 1 line only):
LDA | port | asic | channel | total_lenth[s] | hits | hit_cut | asicHit | acqs | freq | avglen | avAdc | ADCsum |
---|---|---|---|---|---|---|---|---|---|---|---|---|
11 | 2 | 206 | 0 | 1398.279391 | 289 | 175 | 7914 | 86195 | 0.1 | 16.22 | 846 | 244731 |
This file is read by a gnuplot script, that makes a pdf out of it:
gnuplot 5.0 works fine, but version 4.6 doesn't produce individual layer information
Time correlations
LDA time offset
described in setup guide: EUDAQ for AHCAL testbeam
LDA timestamp vs SPIROC TDC:
The data contain all channels of all asics (can be constraind either in the plot or in the correlation script)
Timing statistics
Timing statistics can be obtained either from the BIF raw file, or frmo the AHCAL raw file (then it reads the timestamps from the stream)
${AHCAL-RAWutils}/BIFStats/BIFstats \ --run_number 300 \ --spiroc_raw_file ahcalRaw_Run000300__12p10p2018__08p18p47.raw \ --trig_data_from_spiroc_raw \ --correlation_shift=14102 \
The output provides information in 3 sections:
during reading the data: long gaps (triggers or Readout cycle can be also switched on)
- statistics:
RunNr: Run number
ROCs[count]: number of readout cycles
ROC/s: number of readout cycles per second
Triggers[count]: number of triggers
Length[s]: length of the whole run
AvgROCLength[ms]: average length of the acquisition cycle
ontime[s]: accumulated active time of the SPIROC
ontime[%]: the average duty cycle of the ontime
Triggers/s: the average number of triggers per second
Triggers/ROC: average number of triggers in the readout cycle
Phase: slow clock phase
Start: time of the start of acquisition (relative from the power-on of the LDA/BIF)
ShortStats with all above number tab-separated in a single line.
Phase detail: only 1 phase should be populated throughout the whole testbeam. Can change only when the LDA/BIF is reset / power cycled
Trigger printout
the script will generate a text file with following fields:
- ROC (readout cycle)
- TriggerID: trigger number as saved in the timestamp packet: 16 bits, maximum is therefore 65535, then goes from 0 again
- TS: timestamp of the trigger
- inside_ROC: whether the trigger was inside readout cycle
- ROC_increment (debug info)
- from_start: timestamp from the start of the acquisition fast command
- from_last: time from last trigger (trigger distance)
- bxid: Bunch crossing ID
- time_within_bxid: in what time with regards to the start of the acquisition the trigger cam
following observations can be made from the data:
trigger time distribution:
trigger distances
Start command clock phase consistency
TODO
Custom histograms
DQM4HEP
prerequirement:
Scripts (best executed each line individually in separate tab of a terminal → each line goes to a new terminal tab/window):
Older installation and operation guides
- http://flcwiki.desy.de/tb2018/DAQ_DQM4HEP
- http://flcwiki.desy.de/AHCALMonitoring_DQM4HEP
- (really outdated) http://flcwiki.desy.de/AHCALandHGCALTestBeamCERN2017/DQM4HEP
Important files, that need edit when changing setup
No recompilation is needed. It is a very good to commit and push the changes to the git repository
Quasi-online monitoring
described in separate section (TODO)