Use saved routehandles in fv3 cap init phase #585
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
16 tasks
jkbk2004
requested review from
junwang-noaa,
jkbk2004,
BrianCurtis-NOAA and
DeniseWorthen
|
All test were done for the ufs-wm pr 1434. Please, go ahead to make final comments and approve. |
BrianCurtis-NOAA
approved these changes
Oct 3, 2022
jkbk2004
approved these changes
Oct 3, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 adds new runtime configuration option (use_saved_routehandles:) to the model_configure file, which when set to true will save compute remapping route handles to a file, and use it in the subsequent runs avoiding computation of routehandles again. Subsequent runs must use the same compute and output domains and same domain decomposition.
Is a change of answers expected from this PR? No.
Issue(s) addressed
Link the issues to be closed with this PR, whether in this repository, or in another repository.
(Remember, issues should always be created before starting work on a PR branch!)