-
Notifications
You must be signed in to change notification settings - Fork 317
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
ctsm5.2.0 -- ctsm5.2.mksurfdata #2372
Conversation
…dard scenarios, and add error checking for resolution and scenario
…list, mostly adding an ultra-hi-res option for non-crop present day
…ault, nor ultra-high res
…ault, nor ultra-high res
…ure crop datasets are used for all options if possible
…s do only one resolution so can fit in a reasonable time
…cenarios that put everything into one thing
…etland_iss1886 Resolved conflicts: python/ctsm/test/test_sys_fsurdat_modifier.py python/ctsm/test/testinputs/default_data.cfg python/ctsm/test/testinputs/modify_fsurdat_short.cfg
… NEON server or file length issues
…t and needs to update to Clm60
Update ctsm5.2 branch to ctsm5.1.dev176 and some small updates
I submitted these izumi tests to help get around the glitches that Erik saw on izumi.
I compared to alpha-ctsm5.2.mksrf.27_ctsm5.1.dev176 ("null" test) for now. We can run against other baselines later if we have specific questions or concerns. |
Failure not labeled EXPECTED: |
I see what's up with ERS_D_Ld5.1x1_brazil.I2000Clm50FatesCruRsGs.izumi_nag.clm-FatesColdHydro. It is in the expected fail list, but as a COMPARE_base_rest fail. But, #2373 has it fail at runtime. So I'll update the entry to mention #2373. Thanks for pointing that out @slevis-lmwg |
Thanks for all your work on this Erik, Sam, and many more! |
Description of changes
This pull request will document final steps in the ctsm5.2 branch development before we make the ctsm5.2.0 tag.
Specific notes
Contributors other than yourself, if any:
@mvertens @ekluzek @jedwards4b @billsacks @wwieder @lawrencepj1 @negin513 @dlawrenncar @olyson @keerzhang1 @fang-bowen @Face2sea @adamrher @samsrabin
CTSM Issues Fixed (include github issue #):
Fixes #1903
Fixes #1716
Fixes #1556
Fixes #1878
Fixes #2131
Fixes #2218
Fixes #1483
Fixes #2228
Fixes #90
Fixes #80
Fixes #1878
Pull Requests that comprise this effort:
https://github.com/ESCOMP/CTSM/pulls?q=is%3Apr+base%3Actsm5.2.mksurfdata+is%3Aclosed
#2464
#2447
#2427
#2424
#2417
#2327
#2318
#2164
#2048
#2016
#2008
#1946
#1920
#1890
#1873
#1866
#1853
#1796
#1756
#1748
#1746
#1732
#1728
#1721
#1663
#1586
Are answers expected to change (and if so in what way)?
Yes, more than roundoff for at least the following reasons:
Any User Interface Changes (namelist or namelist defaults changes)?
Testing performed, if any:
most recently for tag
alpha-ctsm5.2.mksrf.20_ctsm5.1.dev163
as documented in Workaround for transient Smallville tests #1673 + testing all new datasets #2318 for example here.