Closed bdorney closed 5 years ago
No code changes necessary for usage?
The default behaviour is still for v2b electronics. The scurve script has an option (--extChanMapping
) to take an externally provided mapping file.
Should this PR accompany a switch from v2b defaults? And/or propagating the extChanMapping
argument to further tools...?
Should this PR accompany a switch from v2b defaults? And/or propagating the extChanMapping argument to further tools...?
No, I just wanted to make sure that if this is merged, it's usable
Description
Based on discussion here I have added the bare minimum stop gap files to reconstruct the mapping for V3 equipped detectors using
HV3b_V*
hybrids (V1 through V4).These files where either produced by @lmoureaux or myself (using the tool designed by @lmoureaux in PR #134) from the official EDMS documents provided by the electronics designers.
Types of changes
Motivation and Context
We need correct mapping files for analysis.