You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For various reasons, it may be necessary to be able to reference some build settings (e.g. build-time flags, compiler, etc.) when setting up and/or running your SRW experiment.
Solution
Take advantage of the existing logic in the top-level CMakeLists.txt to write a yaml file with build settings that can then be easily read by the workflow at both setup- and run-time.
For example, with the new UFS fire build (#1139), it is necessary to check that the weather model has been built with fire capabilities before we generate an experiment with fire settings. It could be used similarly in checks for AQM builds; currently this is not done and so error checking is incomplete. This could also be used to deprecate the need to specify a compiler manually in config.yaml, avoiding potential errors that come from incorrect user settings. And I'm sure there are many other cases where this capability would be useful.
Requirements**
Build settings should be in yaml format so that it can be read like any other SRW settings file. Should include the "application" that was built, compiler, and other build-time settings that would be useful to reference at configure/runtime.
Description
For various reasons, it may be necessary to be able to reference some build settings (e.g. build-time flags, compiler, etc.) when setting up and/or running your SRW experiment.
Solution
Take advantage of the existing logic in the top-level CMakeLists.txt to write a yaml file with build settings that can then be easily read by the workflow at both setup- and run-time.
For example, with the new UFS fire build (#1139), it is necessary to check that the weather model has been built with fire capabilities before we generate an experiment with fire settings. It could be used similarly in checks for AQM builds; currently this is not done and so error checking is incomplete. This could also be used to deprecate the need to specify a compiler manually in
config.yaml
, avoiding potential errors that come from incorrect user settings. And I'm sure there are many other cases where this capability would be useful.Requirements**
Build settings should be in yaml format so that it can be read like any other SRW settings file. Should include the "application" that was built, compiler, and other build-time settings that would be useful to reference at configure/runtime.
Acceptance Criteria (Definition of Done)
Merging of PR #1139
The text was updated successfully, but these errors were encountered: