Use jinja templates instead of @VARNAME@
in config files
#3411
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR:
@MACHINE@
inconfig.base
with jinja template pattern{{ MACHINE }}
setup_expt.py
script is updated to remove custom code that was written to search and replace@VARNAME@
with values from the experiment yamls. Jinja provides a much cleaner way to interface those two..j2
inparm/config/<system>
directory. e.g.config.base
is now namedconfig.base.j2
inparm/config/gfs
. It gets rendered asconfig.base
in the experiment directory aftersetup_expt.py
completes the execution.In addition, this PR also:
create_experiment.py
,setup_expt.py
andsetup_xml.py
.Type of change
Change characteristics
How has this been tested?
Experiment directories were created before and after this change and compared. Changes were in the expected places where template patterns were updated.
Checklist