ctsm5.4.035: Merge b4bdev 20260424#3969
Merged
ekluzek merged 82 commits intoESCOMP:masterfrom Apr 27, 2026
Merged
Conversation
… pass the initial check.
…iy/CTSM into bug-fix/irrigate-fates
…nstants for the dust doc. Removed description of Zender 2003 dust emission scheme in the doc.
Merge b4b-dev to master
…20260409 Merge master ctsm5.4.031 to b4b-dev
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
Co-authored-by: Danny M. Leung <97262277+dmleung@users.noreply.github.com>
…oute Revision of section 2.15 (mizuRoute) in technical note for CLM6
New documentation for the CTSM dust emission module
bug fix to the FATES land use driver input code This PR includes a cherry-picked fix from NorESMhub#209 to address swap in the order of rangeland and pasture in the reading of the landuse drivers
ekluzek
added
enhancement
ekluzek
added
PR status: needs testing
test: aux_clm
github-project-automation
Bot
moved this to Ready to start (or start again)
in CTSM: Upcoming tags
samsrabin
approved these changes
Apr 24, 2026
Member
samsrabin
left a comment
samsrabin
left a comment
There was a problem hiding this comment.
Approving without review, assuming this is a straightforward merge.
github-project-automation
Bot
moved this from Ready to start (or start again)
to In progress - master
in CTSM: Upcoming tags
Contributor
Author
|
There are four tests that are still in the queue on Derecho. But, otherwise all testing looks as expected on both Derecho and Izumi. I might bump the remaining tests to premium if they don't run pretty soon... |
github-project-automation
Bot
moved this from In Progress
to Done
in LMWG: Sprint Planning Board
github-project-automation
Bot
moved this from In progress - master
to Done (non release/external)
in CTSM: Upcoming tags
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes
Update submodules, enforce irrigate to off for FATES transient cases, and several documentation updates. Including a github action that will trigger when a PR has a build failure for the documentation. It will then add a comment to the PR summarizing the error. Hopefully, this will be easier for doc editors to understand what broke in the build for their PR.
When a PR has the "build docs" tests fail, it's hard to figure out why. This PR will make it so that the doc build log is posted in a PR comment after the test failure. Example samsrabin#17 (comment).
Since ctsm5.3.046: patch%itype is set to -999, which produces out-of-bounds error, when running HIST with fates, since the defaults point to irrigate=.true..
Though there is irrigate=.true. in use_cases, all the statements with .true. value have use_crop=.true. which can not be true when fates is on.
PR's:
#3624
#3925
#3955
#3938
#3812
Specific notes
Contributors other than yourself, if any: @dmleung @nmizukami @samsrabin @olyson @mvdebolskiy Claude Sonnet 4.6 and Opus 4.7 1M
CTSM Issues Fixed (include github issue #):
Fixes #3170
Most of #3861 except #3968
Are answers expected to change (and if so in what way)? No
Any User Interface Changes (namelist or namelist defaults changes)? Yes
Change so that irrigate will be false when running with FATES for transient cases
Does this create a need to change or add documentation? Did you do so? No But, there are documentation updates
Testing performed, if any: running regular