Initializing TObjects
Looping over stored events in dacScanTree
fitting DAC vs. ADC distributions
Determining nominal values for bias voltage and/or current settings
Warning: when fitting DAC CFG_BIAS_PRE_I_BIT the fitted value, 274, is outside range the register can hold: [0,255]. It will be replaced by 255.
Writing output data
Info in <TCanvas::Print>: png file /data/bigdisk/GEM-Data-Taking/GE11_QC8//GE11-X-S-INDIA-0002/dacScans/2018.11.30.21.55/SummaryGE11-X-S-INDIA-0002_DACScan_2018.11.30.21.55.png has been created
Analysis completed. Goodbye
2) OH not in chamber config and no calFile is passed
Warning: OH0 not found in chamber name dictionary. The chamber name associated with this OH will be set to 'unknown'.
Skipping OH0, no calibration file
No OHs with a calFile, exiting.
3) OH not in chamber config and calFile is passed
Warning: OH0 not found in chamber name dictionary. The chamber name associated with this OH will be set to 'unknown'.
Initializing TObjects
Looping over stored events in dacScanTree
fitting DAC vs. ADC distributions
Determining nominal values for bias voltage and/or current settings
Warning: when fitting DAC CFG_BIAS_PRE_I_BIT the fitted value, 274, is outside range the register can hold: [0,255]. It will be replaced by 255.
Writing output data
Info in <TCanvas::Print>: png file /data/bigdisk/GEM-Data-Taking/GE11_QC8//unknown/dacScans/2018.11.30.21.55/Summaryunknown_DACScan_2018.11.30.21.55.png has been created
Analysis completed. Goodbye
Screenshots (if appropriate):
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Handles the case when an OH in the input tree is not in the chamber dictionary.
Description
This pull request introduces a
dict_chamberNames
and sets the chamber name tounknown
for OH numbers that are not in thechamber_config
dictionary.Types of changes
Motivation and Context
This pull request resolves https://github.com/cms-gem-daq-project/gem-plotting-tools/issues/173
How Has This Been Tested?
I have tested the script (in a venv) for 3 cases:
1) OH in chamber config
2) OH not in chamber config and no calFile is passed
3) OH not in chamber config and calFile is passed
Screenshots (if appropriate):
Checklist: