-
Notifications
You must be signed in to change notification settings - Fork 343
Oversaturation #3683
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
base: master
Are you sure you want to change the base?
Oversaturation #3683
Conversation
|
Thanks for opening this PR, Sean. Have you done any scientific tests of the code or can you describe expected behavior / answer changes? Would a short SP run be enough to quantify differences? Are we safer doing a BGC run to see if there are C cycle changes? Fixes part two listed in #3679 |
|
CTSM SE meeting 2026-01-08: @wwieder will do some scientific testing. |
| over_saturation = max(h2osoi_liq(c,j)-(eff_porosity(c,j)*m_to_mm*dz(c,j)),0._r8) | ||
| h2osoi_liq(c,j) = min(eff_porosity(c,j)*m_to_mm*dz(c,j), h2osoi_liq(c,j)) | ||
| h2osoi_liq(c,j-1) = h2osoi_liq(c,j-1) + over_saturation | ||
| end do |
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.
@wwieder says this is already happening somewhere else. Let's convert to a function that can be reused.
|
I'm running a 30 year BCG-Crop case from my:
The case directory is: |
Description of changes
Add a correction for oversaturated soil layers immediately after the soil water flux calculation in SoilWaterMovementMod.
Specific notes
Contributors other than yourself, if any:
CTSM Issues Fixed (include github issue #):
Are answers expected to change (and if so in what way)?
Any User Interface Changes (namelist or namelist defaults changes)?
Does this create a need to change or add documentation? Did you do so?
Testing performed, if any:
(List what testing you did to show your changes worked as expected)
(This can be manual testing or running of the different test suites)
(Documentation on system testing is here: https://github.com/ESCOMP/ctsm/wiki/System-Testing-Guide)
(aux_clm on derecho for intel/gnu and izumi for intel/gnu/nag/nvhpc is the standard for tags on master)
NOTE: Be sure to check your coding style against the standard
(https://github.com/ESCOMP/ctsm/wiki/CTSM-coding-guidelines) and review
the list of common problems to watch out for
(https://github.com/ESCOMP/CTSM/wiki/List-of-common-problems).