ctsm5.3.060: Preliminary update of ctsm54 defaults (answer changing) #3268
Conversation
Update ctsm_pylib to 3.13.2
…tsm5.3.040 Update ctsm5.4 alpha branch to latest ctsm5.3.040 version
draft to start updating to CMIP7 data for CTSM5.4
Redo ESCOMP#3085 to ctsm5.4. alpha branch fully this time
Correct urban Mesh file
Changes to MEGAN needed for coupled cases Corrections on how MEGAN coefficients are applied. Depends on the cmeps tag cmeps1.1.1
Remove broken FTorch submodule
alpha-ctsm5.4.CMIP7.02.ctsm5.3.055: Update default settings
Fix clm6 ISSP compset aliases slevis resolved conflicts: tools/mksurfdata_esmf/gen_mksurfdata_namelist.xml
github-project-automation
bot
moved this to Ready to start (or start again)
in CTSM: Upcoming tags
slevis-lmwg
moved this from Ready to start (or start again)
to In progress - master
in CTSM: Upcoming tags
Bring in various cleanup efforts found in previous testing after the chill changes came in Various updates for testing and other problems identified in the cesm3_0_beta04 tag. So fixes and cleanup for usability. Including the following: - Fix SHR_ASSERT so single-point matrix test passes - ne3np4 to namelist_defaults_ctsm.xml and Makefile for PTS mode and add ability - Fixes warm starts in PTS_MODE so that SCAM can use restart files - f19 + f45 16pft fsurdat/landuse files to namelist_defaults_ctsm + Makefile - Changes in the FORTRAN code to properly abort when fire-emission is asked for it can't be provided. Added unit testing for this. slevis resolved conflicts: doc/ChangeLog doc/ChangeSum
|
As in #3206, I get |
ekluzek
left a comment
ekluzek
left a comment
There was a problem hiding this comment.
This is identical to the work on the branch, so in general not a lot to say. But, I think there needs to be one important difference on master.
That is I think we keep the surface datasets all ctsm5.3, rather than updating any to ctsm5.4. This does mean that we'll need to continue to keep the alpha branch up to date and used as the final tag for each CESM alpha tag. But, I think that's OK. If we mix ctsm5.4 datasets into ctsm5.3 tags, it'll be forever confusing as to what datasets are in place for the tags.
So I think we remove those changes, but still include everything else. Including the ctsm5.4 finidat files. We should be able to use them, but each entry needs a use_init_interp=".true." in the XML.
I also was somewhat surprised you had to increase some of the wallclock times on izumi. But, it's not necessarily bad to do so. But, I wanted to ask you about that as to what behavior you saw.
github-project-automation
bot
moved this from In progress - master
to Stalled (needs review, blocked etc.)
in CTSM: Upcoming tags
slevis-lmwg
moved this from Stalled (needs review, blocked etc.)
to In progress - master
in CTSM: Upcoming tags
slevis-lmwg
added
PR status: ready
github-project-automation
bot
moved this from In progress - master
to Done (non release/external)
in CTSM: Upcoming tags
3 participants
Description of changes
Brings to master the work done in #3206, which I merged to the ctsm5.4 alpha branch recently as tag
alpha-ctsm5.4.CMIP7.02.ctsm5.3.055.Allows Cecile to run coupled without having to adjust clm things manually. In particular, updates namelist defaults, including new IC files, that have been limited to the ctsm5.4 branch so far.
Link to the upcoming branch tag for #3206 which I merged to the ctsm5.4 alpha branch recently.
Specific notes
Contributors other than yourself, if any:
@ekluzek @wwieder
CTSM Issues Fixed (include github issue #):
Resolves #3116
Resolves #3005
Are answers expected to change (and if so in what way)? Yes, greater than roundoff, same climate:
Any User Interface Changes (namelist or namelist defaults changes)?
Namelist defaults changes
Does this create a need to change or add documentation? Did you do so?
Probably. Not at this time.
Testing performed, if any:
#3206 testing appears in this post and will be repeated before merging this PR to master.