Closed ElizabethRoseStarling closed 4 years ago
without knowing anything else about the context of this change, coding style consistency would say this change should be nVFATS
-> nVFATs
(and if this change was made to make something match an nVfats
elsewhere, that other location should be changed from nVfats
-> nVFATs
)
The most used variable name is nVFATS
:
[lpetre@gem-daq gem-plotting-tools]$ grep -hori nvfats pkg | sort | uniq -c
15 nVFats
1 nVFATs # which is a comment
99 nVFATS
with nVFats
used mainly in fitting/fitScanData.py
, three times in chamberInfo.py
and once in utils/scurveAlgos.py
(for compatibility with the first file).
I guess the simplest change would be to convert the nVFats
to nVFATS
(which was introduced in the GE2/1 generalizing PR).
The best change for code style consistency would be your suggestion. However, it requires the largest number of changes (with the associated issues) and would probably require changes in the GE2/1 PR from vfatqc-python-scripts
.
The most used variable name is
nVFATS
:[lpetre@gem-daq gem-plotting-tools]$ grep -hori nvfats pkg | sort | uniq -c 15 nVFats 1 nVFATs # which is a comment 99 nVFATS
with
nVFats
used mainly infitting/fitScanData.py
, three times inchamberInfo.py
and once inutils/scurveAlgos.py
(for compatibility with the first file).I guess the simplest change would be to convert the
nVFats
tonVFATS
(which was introduced in the GE2/1 generalizing PR).
:+1: for least invasive correction as a hotfix, with a potential cleanup later
The best change for code style consistency would be your suggestion. However, it requires the largest number of changes (with the associated issues) and would probably require changes in the GE2/1 PR from
vfatqc-python-scripts
.
superseeded by #284
Description
Replaced nVFATS with nVFats in all instances so iterativeTrim.py can function correctly.
Types of changes
Motivation and Context
Fixes Issue 280.
How Has This Been Tested?
Screenshots (if appropriate):
Checklist: