-
Notifications
You must be signed in to change notification settings - Fork 376
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
Exact restart failure for f45_g37
grid for SOIL2N_TNDNCY_VERT_TRANS
for comprehensive FATES testmod
#6125
Comments
Excluding this output variable results in the test passing for this particular resolution even on longer timescales. As no other ERS diffs crop up, my assumption is that this issue is isolated to this particular history output. The issue also appears to geographically isolated, only showing up in one area: Based on that insight, I tested the same configuration, but with a different resolution, this time using the |
f45_g37
grid for SOIL2N_TNDNCY_VERT_TRANS
for comprehensive fates testmodf45_g37
grid for SOIL2N_TNDNCY_VERT_TRANS
for comprehensive FATES testmod
needle in one of a thousand haystacks |
Truth. I should also note that it was only showing up for one decomp dimension as well. |
Interestingly (weirdly), a longer 30 day test does not result in the exact restart failure; everything passes. I'm thinking we should just call this a glitch of some sort and close this out for now. We can open it again if it crops up with a different length test. |
Reopening due to reappearance with #6235 |
I wanted to highlight here this comment from #6235 that may be relevant for future work to address this: |
I'm noticing an interesting RMS diff with the
fates_cold_allvars
ERP testmod results. It failsCOMPARE_base_rest
, but only on a single output:Looking through the
e3sm_land_developer
test output, it appears that the only other testmod that outputs this variable is the SMS smallville test.Originally posted by @glemieux in #6018 (comment)
The text was updated successfully, but these errors were encountered: