Expanding test coverage of ELM-FATES run modes #5548
Comments
peterdschwartz
added a commit
that referenced
this issue
Jan 30, 2024
… next (PR #6018) This pull requests updates the ed_update_site call in elmfates_interfacemod to pass a flag for when this procedure is called during restart. This update should be coordinated with NGEET/fates#1098, which addresses the long duration exact restart issue NGEET/fates#1051. Additionally this pull request resolves #5548 by expanding the fates regression test coverage to include more run mode options for fates at a variety of resolutions and runtimes. [non-BFB] for FATES Fixes #5548
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
FATES has greatly increased the number of modes in which it can be run over the past couple of years. While the fates team has coverage for many of these run modes through other computing assets and host land models, the number of fates specific tests in the elm land developer suite ideally should be increased to provide more coverage for E3SM machines.
Additionally, the fates team should look at expanding the test coverage of the
fatestest suite, to provide another venue for running fates-specific updates (i.e. non-API changing updates to core fates code). Currently we have very good test coverage via clm-fates and we should attempt to reach parity with that list.CC: @rgknox, @peterdschwartz
The text was updated successfully, but these errors were encountered: