-
Notifications
You must be signed in to change notification settings - Fork 312
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
Add long term exact restart test and fixed biogeog + no competition tests to fates suite #1849
Conversation
cime_config/testdefs/testmods_dirs/clm/FatesColdDefReducedComplexNoCompFbg/user_nl_clm
Outdated
Show resolved
Hide resolved
@ekluzek @rgknox what do you think about truncating some of these names? I have run into problems where the length of the testmod name for the reduced complexity modes has caused build errors when I run a single test with a long-ish |
…ests-ers-fbg_nocomp
Per a discussion at the ctsm software meeting a consensus on the truncated naming convention was achieved. |
Per @ekluzek suggestion, I've merged in #1827 into my PR branch and run The fates test mods all have
|
I just noticed I missed that two fates tests are failing for other reasons:
Looking into these as well. |
I guess I missed that this is actually an expected failure: CTSM/cime_config/testdefs/ExpectedTestFails.xml Lines 40 to 45 in 11d589f
Resubmitting it resulted in it passing however. |
The Testing a version of this test as an |
All the other variations result in only |
The issue causing the non-b4b fates The |
Fixes for NEON cases Two sets of fixes for NEON cases: (1) Fixes for leap year handling when there are discrepancies between the model and the DATM forcing data in terms of whether the current year is a leap year. This involved updates to the share and cdeps externals from Jim Edwards. (2) Other fixes for NEON cases from Will Wieder, as documented in ESCOMP#1860
Fix for the non-b4b |
Fates-side PR NGEET/fates#914 fix has been integrated. I will update the externals for this PR to point to the fix tag |
Testing The test locations are here:
Note that the second cheyenne location is the test for the |
Thanks @ekluzek. I'll update the changelog. |
The izumi fates suite tests are showing DIFFs consistent and expected with the DIFFs from the |
I'm still waiting on two tests to clear the queue for the cheyenne fates test suite. Otherwise all tests are passing with BFAILS and DIFFs as expected. |
The last two test passed through the queue. No unexpected issues. This should be good to go now. |
@ekluzek per our google meet conversation here is the test I ran for the mimicsFatesColdDef to enable a baseline comparison with I've renamed the testmod to match the new name convention via 84f768d. I re-ran the testmod to make sure the naming was consistent and would generate the correct name in the |
Description of changes
Adds two 12 month ERS tests to the fates suite along with a new test mod that combines the no competition and fixed biogeography modes as a 30 day ERS test.
Specific notes
The long term ERS test is being added to avoid missing issues related to NGEET/fates#897 in which mid-year restarts were not bfb.
While we include a fates satellite phenology test that exercises fixed biogeography + no competition modes by definition, we should provide additional test coverage for testing these two modes together without being driven by satellite data. This combination is a valid scientific mode in its own right and exercises different code paths.
Contributors other than yourself, if any:
CTSM Issues Fixed (include github issue #):
resolves #1839
resolves #1817
resolves #1551
Are answers expected to change (and if so in what way)? Answers are not expected to change.
Any User Interface Changes (namelist or namelist defaults changes)? No
Testing performed, if any:
TBD
NOTE: Be sure to check your coding style against the standard
(https://github.com/ESCOMP/ctsm/wiki/CTSM-coding-guidelines) and review
the list of common problems to watch out for
(https://github.com/ESCOMP/CTSM/wiki/List-of-common-problems).