ESMF logging and tracing updates around RouteHandle setup #901
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
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
The changes in this PR were made during the debugging effort when testing recent ESMF beta tags. This PR wants to preserve the diagnostic improvements.
The code changes are purely focused at providing improved diagnostic. They do not change the actual implementation of the procedure of setting up the RouteHandles. A few changes to what gets written to ESMF log files during the setup of RouteHandles between FCST and WRT components. Also add a few more ESMF trace regions for more complete coverage in the ESMF profile.