-
Notifications
You must be signed in to change notification settings - Fork 313
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
Fix clm6_0 defaults #2501
Fix clm6_0 defaults #2501
Conversation
In CSEG we decided this is OK to bring in for cesm2_3_beta18 since the CESM coupled compsets use clm5_1. |
I'm a little confused by this last comment. Why is CESM using clm5_1 physics? I thought the whole reason for delaying the alpha17 tag was to get 5.2 datasets onto main to avoid all the source mods and workarounds needed to run a 5.2 dataset with 5.1 physics? Regardless, will the beta17 tag have dead arctic veg modifications active? |
@wwieder this is all something we'll discuss more in depth as a group tomorrow. Yes, I did the update to clm6_0 in ctsm5.2.0 and it naturally fits there -- but was it required and the best time to do it? This will come up in the future so learning here can help us down the road. At ctsm5.2.0 clm5_1 becomes deprecated (see #2379), misnamed, and misleading. A natural thing to think is that clm5_1 would use the clm5_1 surface datasets while clm6_0 uses the newer ones. So at ctsm5.2.0 I removed almost all of the "I compset" Clm51 compsets, and changed all the testing to Clm60. You can still use clm5_1 with long name compsets for "I cases" though. At ctsm5.2.0 it becomes a project for CESM to remove uses of CLM51 in compsets and tests. As you can see from #2379 it will take a while for this to go through CESM. Changes in CESM across components take awhile to happen by nature. But, ctsm5.2.0 is correct when clm5_1 in terms of use of the dead-veg. So the current CAM and CESM compsets will be fine. And that's what will be used for the coupled model testing. Part of what we were looking for on Tuesday at CSEG was to NOT require a tag that was absolutely required for cesm2_3_beta17. This still might make it in though... |
…clm5_1 and clm6_0 physics options is only the params_file which is what's expected this finishes out issues in ESCOMP#2492
…hro compsets to run with RTM as required for Paleo work, best guess as to what needs science support
Merge b4b-dev into master 2024-05-02
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.
@ekluzek thank you for showing me the work that went into this PR.
Make sure CESM testing compsets with cam6 forcing are being exercised. Update NoAnthro to Clm60.
…se of a problem in the use-case changes I made
CTSM5.2 1979 fsurdat and 1979-2026 landuse ne0np4 files + two fixes Includes work by multiple people: @slevis-lmwg: new fsurdat/landuse files and corresponding infrastructure for the three so-called VR grids (ne0np4) @samsrabin: a subset_data fix @olyson: corrections to a couple of history long-names and updates to history_fields_fates.rst and history_fields_nofates.rst
Use ne30np4.pg3_gx1v7 BgcCrop GSWP3v1 finidat file for 1850 clm5_1 and clm6_0.
…o match how the finidat matching is done so that it now works
Summary of aux_clm on izumi... |
Description of changes
Fix namelist defaults for clm6_0 brought in with ctsm5.2.0 as identified in #2492
Specific notes
Contributors other than yourself, if any:
CTSM Issues Fixed (include github issue #):
Fixes #2492
Fixes #2504
Fixes #2519
Fixes #2520
One tick box in #2403
Are answers expected to change (and if so in what way)? Yes! (only for clm6_0 physics though)
Any User Interface Changes (namelist or namelist defaults changes)?
snicar_snobc_intmix, snow_thermal_cond_method, and irrigate
fix use_cases for clm6_0
Testing performed, if any: namelist testing, regular and ctsm_sci test lists