fixes to logging: dbhmax logic and hlm_use_lu_harvest checking#689
Merged
Conversation
…t, now that unit logic is in another variable
rgknox
approved these changes
Sep 1, 2020
Contributor
|
This was tests on fates_main_api hash |
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
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.
Fixes two things: the logic on logging_dbhmax was reversed, and the ok-values checking on hlm_use_lu_harvest wasn't right.
Description:
I worked through all the combinations of possible logic on the dbh checking to make sure it is right this time...
Collaborators:
Both of these were caught by @aldivi.
Expectation of Answer Changes:
not unless logging_dbhmax is set as other than missing value in the parameter file.
Checklist:
Test Results:
not tested yet.
CTSM (or) E3SM (specify which) test hash-tag:
CTSM (or) E3SM (specify which) baseline hash-tag:
FATES baseline hash-tag:
Test Output: