Toward the eventual goal of DB interface all produced TTree objects should have a ChipID branch which stores the hex VFAT as a type int as this will be properly interpreted when casting back to hex.
Types of issue
[ ] Bug report (report an issue with the code)
[X] Feature request (request for change which adds functionality)
There is no way to track which VFAT hybrids were used with a given scan. This is especially important for test stands in which this could change more readily; but this would also be important for P5 (e.g. linking ADC calibration data for a given VFAT).
Brief summary of issue
Toward the eventual goal of DB interface all produced
TTree
objects should have aChipID
branch which stores the hex VFAT as a typeint
as this will be properly interpreted when casting back tohex
.Types of issue
Expected Behavior
All
TTree
objects have:Which is later filled in the appropriate locations. For example the syntax would be:
Current Behavior
There is no way to track which VFAT hybrids were used with a given scan. This is especially important for test stands in which this could change more readily; but this would also be important for P5 (e.g. linking ADC calibration data for a given VFAT).
Context (for feature requests)
Towards the long-term goal of DB integration