zdc calibration workflows
DCS DP processing:
Local example workflow with local CCDB (running on port 8080) :
This will read the list of DPs to be associated to zdc from CCDB (remove --use-ccdb-to-configure if you don't want this, but use hardcoded aliases. You can specify the path of CCDB also with --ccdb-path. YOu can also specify to run in verbose mode (--use-verbose-mode)
o2-calibration-zdc-dcs-sim-workflow --max-timeframes 3 --delta-fraction 0.5 -b |
o2-calibration-zdc-dcs-workflow --use-ccdb-to-configure -b |
o2-calibration-ccdb-populator-workflow --ccdb-path="http://localhost:8080" -b
or
o2-calibration-zdc-dcs-sim-workflow --max-timeframes 3 --delta-fraction 0.5 -b |
o2-calibration-zdc-dcs-workflow -b |
o2-calibration-ccdb-populator-workflow --ccdb-path="http://localhost:8080" -b
To populate locally a DCS entry for the configuration, run the:
O2/Detectors/ZDC/calibration/macros/makeCCDBEntryForDCS.C
macro.
LHC phase:
This will process the LHC phase simulated by the Generator workflow
LHC phase
o2-calibration-data-generator-workflow --lanes 10 --mean-latency 100000 --max-timeframes 500 |
o2-calibration-lhc-clockphase-workflow --tf-per-slot 20 |
o2-calibration-ccdb-populator-workflow --ccdb-path localhost:8080
zdc channel calibration:
To obtain the zdc channel offsets (at end of processing). Input from simulation, but is should work if attached to reco+calib flow
- simulating reading from ccdb, and using it, with "-b", in "test" mode --> to use this, we need an appropriate CCDB object in the CCDB
o2-calibration-data-generator-workflow --lanes 10 --mean-latency 100000 --max-timeframes 500 --do-zdc-channel-calib --do-zdc-channel-calib-in-test-mode -b |
o2-testworkflows-zdc-dummy-ccdb -b |
o2-calibration-zdc-channel-calib-workflow --min-entries 50 --do-zdc-channel-calib-in-test-mode --use-ccdb -b |
o2-calibration-ccdb-populator-workflow --ccdb-path localhost:8080 -b
- simulating reading from ccdb, but not using it, with "-b", in "test" mode --> to use this, we need an appropriate CCDB object in the CCDB
o2-calibration-data-generator-workflow --lanes 10 --mean-latency 100000 --max-timeframes 500 --do-zdc-channel-calib --do-zdc-channel-calib-in-test-mode -b |
o2-testworkflows-zdc-dummy-ccdb -b
| o2-calibration-zdc-channel-calib-workflow --min-entries 50 --do-zdc-channel-calib-in-test-mode -b
| o2-calibration-ccdb-populator-workflow --ccdb-path localhost:8080 -b
- Using the workflow that has both LHCclockPhase and zdcChannelCalib; for now I can enable only one, or the CCDB populator will not work
o2-calibration-data-generator-workflow --lanes 10 --mean-latency 100000 --max-timeframes 500 --do-zdc-channel-calib --do-zdc-channel-calib-in-test-mode -b |
o2-calibration-zdc-dummy-ccdb-for-calib -b |
o2-calibration-zdc-calib-workflow --do-channel-offset --min-entries 50 --do-zdc-channel-calib-in-test-mode -b |
o2-calibration-ccdb-populator-workflow --ccdb-path localhost:8080 -b
- same as above, enabling CCDB
o2-calibration-data-generator-workflow --lanes 10 --mean-latency 100000 --max-timeframes 500 --do-zdc-channel-calib --do-zdc-channel-calib-in-test-mode -b |
o2-calibration-zdc-dummy-ccdb-for-calib -b |
o2-calibration-zdc-calib-workflow --do-channel-offset --use-ccdb --min-entries 50 --do-zdc-channel-calib-in-test-mode -b |
o2-calibration-ccdb-populator-workflow --ccdb-path localhost:8080 -b
By default the rate of the TF sampling will match to mean-latence / lanes, so that the sampling and generation are balanced and no TF is dropped out at the generation level. One can provide the option --pressure <float, D=1.>, in which case the sampling rate will be increased by this factor, creating a back-pressure on the processing due to its latency.
There is a possibility to generate data in multiple independent workflows, still avoiding TF-s with the same ID in different workflow. Options --gen-norm <N, D=1> --gen-slot <I,D=0> will enforce skipping all TF-s except those with (TFID/lanes)N == I. I.e. for example, to emulate the processing with 3 different EPN's with 8 lanes each one can run in 3 terminals:
# Term.1: will produce TFs [0:7], [24:31], [48:55] ...
o2-calibration-data-generator-workflow --lanes 8 --max-timeframes 5000 --gen-norm 3 --gen-slot 0
# Term.2: will produce TFs [8:15], [32,39], [56:63] ...
o2-calibration-data-generator-workflow --lanes 8 --max-timeframes 5000 --gen-norm 3 --gen-slot 1
# Term.3: will produce TFs [16:23], [40:47], [64:71] ...
o2-calibration-data-generator-workflow --lanes 8 --max-timeframes 5000 --gen-norm 3 --gen-slot 2
TimeSlewing:
For Time Slewing. Will save the Time Slewing information in files when a certain condition is reached. A post-processing should then take care of extracting the CCDB
shell
o2-calibration-data-generator-workflow --lanes 10 --mean-latency 100000 --max-timeframes 10 -b |
o2-calibration-zdc-collect-calib-workflow --tf-sending-policy --running-in-test-mode -b
* non-test but simplified (using option "is-max-number-hits-to-fill-tree-absolute"):
shell o2-calibration-data-generator-workflow –lanes 10 –mean-latency 100000 –max-timeframes 10 -b | o2-calibration-zdc-collect-calib-workflow –max-number-hits-to-fill-tree 300 –is-max-number-hits-to-fill-tree-absolute -b ~~~
1.9.8 