You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 31, 2022. It is now read-only.
Brief summary of issue
The channel to strip mapping is not presently correct for v3 electronics, and in many cases it's hard coded to v2b mapping.
Types of issue
Expected Behavior
The channel-to-strip mapping should stop defaulting to the v2b mapping but should be determined in the following way:
--extChanMapping
),--extChanMapping
.To accomplish this I would propose the getMapping(...) function is adapted to use the db interface tools to determine the mapping.
This may require adding a function to extract the channel mapping from the DB and then getMapping(...) to use this function.
Current Behavior
anaSBitReadout.py
Here the mapping is v3 defaulted. But it is hard coded for HV3b_V1, V2, or V4 hybrids:
gem-plotting-tools/anaSBitReadout.py
Lines 97 to 102 in 78c8874
anaUltraScurve.py
Here an external mapping file can be provided but otherwise it will default to the v2b mapping:
gem-plotting-tools/anaUltraScurve.py
Lines 293 to 298 in 78c8874
anaUltraThreshold.py
The mapping is defaulting to the v2b mapping:
gem-plotting-tools/anaUltraThreshold.py
Lines 65 to 70 in 78c8874
Context (for feature requests)
The channel to strip mapping is not presented correctly for v3 detectors.
Your Environment
The text was updated successfully, but these errors were encountered: