-
Notifications
You must be signed in to change notification settings - Fork 26
chConfig produced file not compatible #278
Comments
@giovanni-mocellin are the package versions (with |
I believe the issue is due to conversion from the % string formatting to the gem-plotting-tools/utils/scurveAlgos.py Lines 905 to 913 in bbc3e25
Since the file |
@dteague do you think you could address this quickly? |
Looking into this now! |
Brief summary of issue
Running the analysis of scurves (in QC7 machine) produces now chConfig files that contain the column "mask" for the channels the booleans "True" and "False", instead of 1 and 0.
This makes impossible a configuration with chConfig in QC8, since confAllChambers crashes requiring a number and not a boolean.
Types of issue
Expected Behavior
The chConfig files produced by the scurves analysis should have the "I:mask" column with numbers 0 or 1.
Current Behavior
The chConfig files produced by the scurves analysis now have the "I:mask" column with "False" or "True".
Steps to Reproduce (for bugs)
Possible Solution (for bugs)
Make sure that the code is writing the boolean for the mask as an integer number
Context (for feature requests)
When analyzing a single scurve, one can use "sed" command to change that and then anything that uses the chConfig works.
But, if one tries to run the trimming, it might get stuck since it cannot configure the chambers with the chConfig derived from the previous scurve.
Your Environment
The text was updated successfully, but these errors were encountered: