review names of constants
awegsche opened this issue · comments
The following constants need pre- (or suf-)fixes stating their intention (e.g. COL
or COLUMN
for column names, SUF
or SUFFIX
for a suffix etc):
omc3/omc3/optics_measurements/constants.py
Lines 21 to 51 in 6763e86
I am currently consolidating constants.
maybe we could combine this issue with #231 and #305 (and similar issues that I may have overlooked) to something á la restructure column naming
, also in view of having one constants dir for all the const (correction, kmod, optics_meas)
the problem, for now, is still that the order of where to put these -fixes is still up to the implementer for the specific module.
Maybe some simple functions could be written to also define the order in the constants module, e.g. an err_column(var)
fct which returns f"{ERR}{var}"
.. or alternative, and a lot more type work, spell out every column as constant here
maybe we could combine this issue with #231 and #305 (and similar issues that I may have overlooked) to something á la
restructure column naming
, also in view of having one constants dir for all the const (correction, kmod, optics_meas) the problem, for now, is still that the order of where to put these -fixes is still up to the implementer for the specific module. Maybe some simple functions could be written to also define the order in the constants module, e.g. anerr_column(var)
fct which returnsf"{ERR}{var}"
.. or alternative, and a lot more type work, spell out every column as constant here
We shouldn't bundle together issues and pull requests. I deliberately opened this as separate issue to avoid discussions on this one blocking other, more important issues like #305.
I agree that we should go for atomic PRs. I am also not a fan of having functions in the constants modules.