-
Notifications
You must be signed in to change notification settings - Fork 360
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 testmods to fates
regression test to increase coverage and include long-term exact restart fix
#6018
Add testmods to fates
regression test to increase coverage and include long-term exact restart fix
#6018
Conversation
Below is the current list of existing clm-fates testmods. Ideally we would have parity between host land models. To include:
Site aliases that do not work currently (see #4718):
No equivalent elm-fates mode:
ctsm-fates specific compset:
No
Has duplicate testmod with slightly different ctsm compset already included above:
|
fates
regression test suite to increase FATES run mode coveragefates
regression test to increase coverage and include long-term exact restart fix
Initial testing with a truncated set of the above list is showing good results. Only two tests failed |
UPDATE: we'll take care of this in a different PR |
@rljacob I noticed from the email listserv that there is consideration for removing support for |
@glemieux I've updated that and we'll keep ne4 but for an atmosphere only test. You should try ne4pg2 which is the finite volume version of the plain "ne4" and will be our standard low resolution grid. |
fates
regression test to increase coverage and include long-term exact restart fixfates
regression test to increase coverage and include long-term exact restart fix
deafaa8
to
64aba52
Compare
Adding a note that given the lack of a supported single site, we're not including fates hydro tests yet. |
@peterdschwartz @bishtgautam this PR is ready for review. In particular, @rgknox and I would like know what you think about the fates testmods that we added to the As an aside, I'm wondering if there might be support for addressing #4718 such that we could add |
I'm noticing an interesting RMS diff with the
Looking through the @rgknox is this something to be concerned about? |
Waiting on perlmutter to come back up to check the status of the |
notes: perlmutter back up so can work on it again. |
@ckoven and @rgknox the results from the elm-only tests that I've run don't show differences in the exact restart, so I'm currently thinking that this specific to fates. Inspecting the files, it looks like the difference is in one grid cell, for the first levdcmp dimension only (at least for this short nine day test). |
d09e04f
to
702d8b2
Compare
794f3c8
to
435aded
Compare
@peterdschwartz I've worked around issue #6125 by changing the grid resolution for the |
@peterdschwartz this is ready for review and merge |
Adds multiple fates testmods to provide a more comprehensive set of cases to exercise a variety fates run modes. The fates test list is expanded to encompass all the new testmods. The elm land developer test list has been updated with a subset of these new fates tesmods to provide more baseline coverage. This also updates all fates tests to run as double precision. Finally, this commit provides a minor FATES API update to incorporate a fates fix to an issue seen with long-duration exact restarts.
360b1f8
to
b570e71
Compare
Final testing of UPDATE: a bunch of tests still sitting in queue. Should have updates tomorrow morning. |
Regression testing on perlmutter against the master baseline is returning b4b for all tests. The new fates testmods that have been added return an expected |
Testing on chrysalis after merging and the
|
@glemieux Looks like this test is the only fates test with nthreads=2. |
@peterdschwartz Good catch. I missed that #4283 has been an outstanding issue. I wonder why this is passing on perlmutter but not on chrysalis. |
The clump decomposition should be the same for fates and the base land model... Maybe something is getting bypassed or missed when the use_fates switch is on that would had otherwise ran for non-fates ELM. It might be work running this same test without FATES to see if the same error triggers. |
@peterdschwartz I'll update the offending testmod to run with single threading for now. I should be able to update this today. |
Great! also, it doesn't appear to have been using fates at all. Likely because the |
That was intentional since the @peterdschwartz is there any other testing from me that is necessary? |
Test passed on chrysalis as well so this should be ready to merge to next |
… 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
Merged to next. |
@glemieux
Backtrace points to |
@glemieux Do you still have directory of a successfully running this case on pm-cpu? Might be helpful to compare the software environments to see if that is the issue. |
@peterdschwartz here's the location on perlmutter where I retested perlmutter location: |
I wonder if the "numeric conversion not representable" is coming up because a nan or inf is in the array somewhere. We initialize some fates variables with nan. |
The debug run didn't report anything different, but manually zeroing out |
@rljacob @rgknox While debugging, I noticed the carbon balance checking algorithm in ELM is wrong. This is an error independent from this PR and fixing it is likely non-BFB for some cases, so I will make an Issue and work on a PR for that bug separately. |
Moved from col_cf_setvalues to col_cf_zero_forfates_veg
Re-merged to fix fates_cold_allvars test
Re-merged to next |
merged to master and bless requests submitted |
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.
[nonBFB] for FATES
Fixes #5548