Bring additional changes to support UFS Coastal App #1255
Closed
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.
Pull Request Summary
This PR aims to bring minor modifications to support UFS Coastal App specific model configurations.
Description
Following is the list of the changes,
BUILD_TOOLS
option is included to build system to build tools. This isOFF
by default and does not change the current behavior.SCRIP
andSCRIPNC
tomodel/bin/switch_meshcap_pdlib
switch file since the mesh file was not generated by default. If this is not right way to do it maybe we could create another copy of this file and point that one under UFS Coastal App.model/src/wav_comp_nuopc.F90
is modified to support standalone runs under ufs-weather-model. Oncestandalone
option under wave section ofufs.configure
is set totrue
, then the model reads its own forcing rather than getting data from coupling. So, this will allow standalone wave configurations without any other component.Sw_wavsuu
,Sw_wavsuv
andSw_wavsvv
) in a correct way. This is tested with SCHSIM ocean model coupling with DATM+SCHSIM+WW3 configuration.Issue(s) addressed
Commit Message
Check list
Testing
How were these changes tested?
The changes are tested under UFS Coastal App.
Are the changes covered by regression tests? (If not, why? Do new tests need to be added?)
Have the matrix regression tests been run (if yes, please note HPC and compiler)?
Please indicate the expected changes in the regression test output, (Note the list of known non-identical tests.)
Please provide the summary output of matrix.comp (matrix.Diff.txt, matrixCompFull.txt and matrixCompSummary.txt):