Tags: ESCOMP/CTSM

Move $nl_flags->{'use_hillslope'} to a more effective spot

The move allows hillslope_fsat_equals_zero to equal = .true. when use_hillslope = .true. as originally intended.

Answers change for Hillslope cases only; the changes are greater than roundoff.

PR #4046
Issue 4030

b4b-dev merge; mostly docs, some tools/ cleanup.

Update clm6 paramfiles and add new paramfile for hillslope hydrology

PR #4029
Issue #3659
Changes answers more than roundoff for clm6 cases.

Add new fates namelist switch for dbh init when nocomp is on

This change is coordinated with FATES PR NGEET/fates#1550. Adds a switch (use_fates_dbh_ini) for initializing patches with dbh instead of density for nocomp runs. Switch is off by default resulting in no change in answers.

PR #3910

Merge b4b-dev to master

Details in PR #4000

Fix for FATES year-boundary restart issue

Complete the FATES-CLM nitrogen coupling

PR #3409. Description:
Intoduce code, namelist option, and tests on the CLM side to accommodate interactive nitrogen with FATES.

Roundoff changes for most cases, though not for Sp and FatesSp.

The FATES side PR is NGEET/fates#1472. Fates got updated from sci.1.92.1_api.44.1.0 to sci.1.92.4_api.45.0.0.

Supporting information (other than in the issue referenced below):
- Nutrient enabled FATES handbook: https://docs.google.com/document/d/1I35fGDfKTkn9_8Z6qXot7HZf3ICSpLONd-iFEErAh0k/edit?usp=drive_link
- FATES CLM N coupling: https://docs.google.com/document/d/1mpBtpCLGJpAGw6R3-nGGY92IWRU3ISvaAUKxvcDVJRw/edit?usp=drive_link

Resolves issue #3378.

Merge b4b-dev to master

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.

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

b4b: Change some local vars to global to add to history

PR #3933