ctsm5.3.083
1 view
Skip to first unread message
CTSM Gatekeeper
Oct 29, 2025, 6:54:04 PM10/29/25
to ctsm...@ucar.edu
*** RESPONSES TO THIS EMAIL WILL NOT BE READ ***
===============================================================
Tag name: ctsm5.3.083
Originator(s): rgknox (Ryan Knox,LAWRENCE BERKELEY NATIONAL LABORATORY,510-495-2153)
Date: Wed 29 Oct 2025 03:35:50 PM MDT
One-line Summary: Changes to coupling of supplementation status with FATES.
Purpose and description of changes
----------------------------------
Supplementation status is now passed to FATES as a run-time boundary condition. This set of changes is synchronized with FATES-side changes that were oriented around how supplementation status impacts whether or not fine-root proportions are allowed to change during CNP runs.
Significant changes to scientifically-supported configurations
--------------------------------------------------------------
Does this tag change answers significantly for any of the following physics configurations? No
Bugs fixed
----------
No bugs were fixed.
Notes of particular relevance for users
---------------------------------------
When CTSM-FATES has nutrient coupling, note that FATES plants will default to not changing L2FR when supplementing nitrogen.
Caveats for users (e.g., need to interpolate initial conditions): None
Changes to CTSM's user interface (e.g., new/renamed XML or namelist variables): None
Changes made to namelist defaults (e.g., changed parameter values): None
Changes to the datasets (e.g., parameter, surface or initial files): None
Changes to documentation: None necessary.
Substantial timing or memory changes: None
Notes of particular relevance for developers:
---------------------------------------------
We had been passing a stealth namelist variable from CTSM to FATES, it gave FATES information about what types of mineralized nutrient were available (ie NO3 or NH4), but FATES has never used this information, so it was removed.
Caveats for developers (e.g., code that is duplicated that requires double maintenance): None
Changes to tests or testing: None
Testing summary:
----------------
regular tests (aux_clm: https://github.com/ESCOMP/CTSM/wiki/System-Testing-Guide#pre-merge-system-testing):
derecho ----- OK
izumi ------- OK
fates tests: (give name of baseline if different from CTSM tagname, normally fates baselines are fates-<FATES TAG>-<CTSM TAG>)
derecho ----- OK
izumi ------- OK
Answer changes
--------------
Changes answers relative to baseline: No answer changes with one exception. Some FATES-specific variables related to radiation diagnostics and error tracking changed with updating the FATES tag. These were diagnostic only changes, and not related to FATES internals changing in any way.
ther details
-------------
Pull Requests that document the changes (include PR ids):
https://github.com/ESCOMP/CTSM/pull/3348
===============================================================
===============================================================
===============================================================
Tag name: ctsm5.3.083
Originator(s): rgknox (Ryan Knox,LAWRENCE BERKELEY NATIONAL LABORATORY,510-495-2153)
Date: Wed 29 Oct 2025 03:35:50 PM MDT
One-line Summary: Changes to coupling of supplementation status with FATES.
Purpose and description of changes
----------------------------------
Supplementation status is now passed to FATES as a run-time boundary condition. This set of changes is synchronized with FATES-side changes that were oriented around how supplementation status impacts whether or not fine-root proportions are allowed to change during CNP runs.
Significant changes to scientifically-supported configurations
--------------------------------------------------------------
Does this tag change answers significantly for any of the following physics configurations? No
Bugs fixed
----------
No bugs were fixed.
Notes of particular relevance for users
---------------------------------------
When CTSM-FATES has nutrient coupling, note that FATES plants will default to not changing L2FR when supplementing nitrogen.
Caveats for users (e.g., need to interpolate initial conditions): None
Changes to CTSM's user interface (e.g., new/renamed XML or namelist variables): None
Changes made to namelist defaults (e.g., changed parameter values): None
Changes to the datasets (e.g., parameter, surface or initial files): None
Changes to documentation: None necessary.
Substantial timing or memory changes: None
Notes of particular relevance for developers:
---------------------------------------------
We had been passing a stealth namelist variable from CTSM to FATES, it gave FATES information about what types of mineralized nutrient were available (ie NO3 or NH4), but FATES has never used this information, so it was removed.
Caveats for developers (e.g., code that is duplicated that requires double maintenance): None
Changes to tests or testing: None
Testing summary:
----------------
regular tests (aux_clm: https://github.com/ESCOMP/CTSM/wiki/System-Testing-Guide#pre-merge-system-testing):
derecho ----- OK
izumi ------- OK
fates tests: (give name of baseline if different from CTSM tagname, normally fates baselines are fates-<FATES TAG>-<CTSM TAG>)
derecho ----- OK
izumi ------- OK
Answer changes
--------------
Changes answers relative to baseline: No answer changes with one exception. Some FATES-specific variables related to radiation diagnostics and error tracking changed with updating the FATES tag. These were diagnostic only changes, and not related to FATES internals changing in any way.
ther details
-------------
Pull Requests that document the changes (include PR ids):
https://github.com/ESCOMP/CTSM/pull/3348
===============================================================
===============================================================
Reply all
Reply to author
Forward
0 new messages