Move fixed-file mapping variables out of config_defaults.yaml.#421
Conversation
config_defaults.yaml.
|
Machine: hera |
|
Machine: jet |
b99a305 to
58614d8
Compare
Also, move other variables that are unlikely/never changed by user.
58614d8 to
13d5512
Compare
525dc29 to
e64be4c
Compare
ebd2555 to
4c02e37
Compare
MichaelLueken
left a comment
There was a problem hiding this comment.
@danielabdi-noaa Nice work! I have some comments, but everything looks good.
| f''' | ||
| The specified configuration file does not exist: | ||
| "{config_file}"''' |
There was a problem hiding this comment.
For consistency, would it be better to convert the single quotes to double quotes, then convert the double quotes around {config_file} to single quotes?
There was a problem hiding this comment.
Note that I did not make these changes by hand, but run a python code formatter on all python files usingblack --safe. I do this from time to time but we should probably apply this on the client/server side and force a coding/formatting standard. Black has a preference for double quotes (single or triple) over single quotes which is why you are seeing those changes.
There was a problem hiding this comment.
Thanks for the information about the black python code formatter. From StackOverflow, using Git hooks, it looks like it would be possible to run black on the python scripts before committing changes. Is this python code formatter available on RDHPCS machines, or is this something that you run on your own machine before creating the PR? If it is available on RDHPCS, then it should be fairly easy to set up a Git hook to run before committing (create a .git/hooks/pre-commit hook to use the formatter on the python files).
Do we want to use black, or is there another python code formatter that might be better? Do we want to enforce what black recommends, or create our own standard?
I think this would be a good topic for the SRW meeting this week.
There was a problem hiding this comment.
@MichaelLueken I think that is a good idea! black is not available on RDHPCS machines as far as I know but we can use flake8 or something similar.
80b2cc0 to
093b146
Compare
d78f94e to
12c41c6
Compare
MichaelLueken
left a comment
There was a problem hiding this comment.
Thanks, @danielabdi-noaa, for addressing my concerns. I approve of this update.
DESCRIPTION OF CHANGES:
This PR mainly addresses issue #367. Fixed files mapping arrays are something that are probably never changed by the user so they don't belog there
fixed_files_mapping.yaml)set_extrn_mdl_params.pyas it barely does anythingOther mis-placed variables in config_defaults will be moved as I find them
Type of change
TESTS CONDUCTED:
DEPENDENCIES:
None
DOCUMENTATION:
None
ISSUE:
config_defaults.yaml#367CHECKLIST
LABELS (optional):
A Code Manager needs to add the following labels to this PR:
CONTRIBUTORS (optional):
@gspetro-NOAA