-
Notifications
You must be signed in to change notification settings - Fork 321
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
Merge fates_main_api into master #1264
Merge fates_main_api into master #1264
Conversation
gnu test suite. Changing highest res grid test to clm5.
… hydro is active.
…uper-saturation during plant hydraulics.
variables that track size and age dependent mortality. Add coage dimension to clmfates_interfaceMod.F90 and histFileMod.F90. This allows cohort age to be tracked. Also add variables that allow size and age dependent mortality to be tracked. These mortality functions have been added to the fates code.
[Cohort age tracking is now a flag like spitfire or hydro that can be turned on with the flag hlm_use_cohort_age_tracking. These changes add this flag to ctsm code. This is for use when FATES is running.] Fixes: [NGT-ED Github issue #] User interface changes?: [No - only on the FATES side of things] Code review: [Names] Test suite: [suite name, machine, compilers] Test baseline: Test namelist changes: Test answer changes: [bit for bit, roundoff, climate changing] Test summary: No testing.
[ Add NPLANT_CAPF to user_nl_clm - number of plants by cohort age class and pft. ] Fixes: [NGT-ED Github issue #] User interface changes?: [No] Code review: [Names] Test suite: [suite name, machine, compilers] Test baseline: Test namelist changes: Test answer changes: [bit for bit, roundoff, climate changing] Test summary:No testing.
…olidate the initialization sequence, and also reduce fates side circular dependencies. This also fixes a bug where some parteh structures were not being passed to this history dimensions properly.
I've done some work on the build-namelist tests, and found some issues that definitely need some attention. So it'll be good to get these changes in place. A lot of the fates tests weren't working because of this, so this will be good to have in. |
Rerunning all tests.
|
There are a number of failures for the
|
@ekluzek noted that the |
…spitfire settings that don't need it to 'none' when light_res is none do not set any of the lighting settings, remove use_cn setting for lightning as not needed
…x/CTSM into fates_main_api-merge-ctsm_master
…on't have to have a different copy for each
The
NOTE: the debug version of these tests PASS, although only a subset of the failing list have debug versions. @ekluzek and I chatted a bit about this. One test was to see if we could simply update the nag compiler to 7.0. I attempted to do this for both this PR branch and master, but both of them are failing at the same point in the mct build process. Troubleshooting this line is beyond my capabilities I think. The other option we considered was trying to see if there is a version of fates_main_api with PRTAllometricCNPMod that might pass this test on izumi. I'm currently looking into this. |
@billsacks per our conversation at the ctsm software meeting here are the nag tests that are failing
Note that it looks like only |
There is a compiler error with nag when building in non-debug mode with the latest FATES code. The non-debug nag tests don't seem to have much value, so I'm removing them - either changing them to debug tests or removing them entirely, depending on whether a given configuration seems to have sufficient test coverage.
@glemieux you'll get BFAIL results (due to missing baselines) for the new tests. I checked the test list, and I think we have sufficient coverage of these configurations in other tests that you don't need to worry about this - i.e., you do not need to generate baselines for these tests from master. |
@billsacks thanks! @ekluzek I'll rerun the |
Re-ran |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, most things I asked for were addressed. We moved a few things to their own issues to be done later. But, this is an exciting development for CTSM and FATES so good to have this tag in place!
WHAT! This is awesome news. Thanks for all your hard work on this.
…On Fri, Feb 5, 2021 at 12:06 AM Erik Kluzek ***@***.***> wrote:
Merged #1264 <#1264> into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1264 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5IWJHSK5D56PESGLVMGPLS5OKJDANCNFSM4WU4HOMA>
.
|
Description of changes
This PR merges fates_main_api into master. The fates_main_api branch has integrated updates from master up to tag ctsm5.1.dev020 per PR #1257. The purpose of this merge is to bring the most recent fates updates into master and for fates future development to continue from ctsm master instead of on fates_main_api.
Specific notes
The
aux_clm
suite tests were compared againstctsm5.1.dev021
baseline. Thefates
suite tests were compared againstfates-sci.1.43.2_api.14.2.0-ctsm5.1.dev020-C5f348cac-F5534a940
baseline.Contributors other than yourself, if any: @ekluzek
CTSM Issues Fixed (include github issue #): none
Are answers expected to change (and if so in what way)? Only for
aux_clm
fates testmods only. All else b4b.Any User Interface Changes (namelist or namelist defaults changes)? none
Testing performed, if any:
aux_clm
on cheyenne:/glade/u/home/glemieux/scratch/tests_0126-161304ch
aux_clm
on izumi:/scratch/cluster/glemieux/tests_0204-142628iz
fates
on cheyenne:/glade/u/home/glemieux/scratch/clmed-tests/basegen.fates-sci.1.43.2_api.14.2.0-ctsm5.1.dev021-C4c9a4c15-F5534a940
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).