Split associate statement to avoid NAG compiler line continuation issue#1009
Merged
Conversation
The nag compiler has a limit on the number of line continuations
Contributor
Author
The user should be directed to update the HLM specific name for the namelist variable, not the intermediate variable that is used to pass the setting value from the hlm to fates. See clm_varctl.F90 for definitions.
rgknox
approved these changes
Apr 3, 2023
Contributor
Author
|
Regression testing on cheyenne is complete. All expected tests pass B4B. Folder: |
This file contains hidden or 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
2 participants
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:
Fixes #1010 by splitting the
associatestatement up into multipleassociatecalls. The split was made at what appears to be the maximum number of line continuations that the nag compiler will allow.Also includes simple b4b updates for the following:
Collaborators:
@ekluzek
Expectation of Answer Changes:
Should be B4B
Checklist:
Test Results:
TBD
CTSM (or) E3SM (specify which) test hash-tag:
CTSM (or) E3SM (specify which) baseline hash-tag:
FATES baseline hash-tag:
Test Output: