-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Small updates to output variables, addition of FATES_FRACTION variable #854
Conversation
I'd planning on coordinating this PR with ESCOMP/CTSM#1515 to update the history variable names in the ctsm test mods. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!!! Thank you!!
Aside from the expected
UPDATE: Test results for |
The izumi version of
Interestingly, this isn't an issue with the intel version on Cheyenne (which is where the original issue was discovered). I will run this test on the intel compiler on izumi to rule out machine differences. |
The intel version of this test was a bust. It's failing out very early due to some ESMF io errors. Output is here: |
This set of changes allows the harvesting module to pass products back to the host. API modifications are still required in CLM, but this feature should work fully with ELM.
Aside from the expected
The one test not b4b is failing to run on Izumi:
UPDATE: writing out the |
@rgknox the issue appears to be with the |
Retesting after applying 9d9c192, File locations:
|
This updates a few output variable names and metadata based on some typos that were found, plus adds an additional variable
FATES_FRACTION
which is the fraction of the HLM gridcell occupied by FATES.Description:
We create an
hio_fates_fraction_si
variable which is set to 1.0, since it will be zero (see below) on non-fates columns. The average will then be the total gridcell fates fraction. (see here)Because of our previous history interface update which flushes all FATES variables to the
hlm_hio_ignore_val
, we needed to flush this specific variable to zero for this method to work. I added an optionalflush_to_zero
argument to theset_history_var
subroutine (here) which will prompt the subroutine to flush that variable to zero.Collaborators:
@ckoven
Expectation of Answer Changes:
None, only change should an additional variable and some small changes to variable names and metadata.
Checklist:
Test Results:
CTSM (or) E3SM (specify which) test hash-tag:
CTSM (or) E3SM (specify which) baseline hash-tag:
FATES baseline hash-tag:
Test Output: