Skip to content
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

Bring the carbon isotope fix to the release branch #698

Merged
merged 10 commits into from
May 8, 2019

Conversation

ekluzek
Copy link
Collaborator

@ekluzek ekluzek commented Apr 26, 2019

Description of changes

Fix the Carbon isotope bug for transient land-use change on the release branch (brings in changes from ctsm1.0.dev036 to release branch).

Specific notes

We currently have a bug so that for transient land-use change cases answers are different starting in soil
carbon when Carbon isotopes (use_c13, or use_c14) are on versus off. Answers are identical if there is no
land-use change. The bug does cause bulk Carbon (C12) to be slightly different, but qualitatively the same.
There is a significant impact to the Carbon isotope simulation however. The bug was causing changes in isotopic
pools to be directed to the bulk Carbon. Because, isotopes are so much smaller than bulk Carbon, this doesn't
cause a marked difference in the bulk Carbon simulation. But, the lack of the change in the isotopic pool
does have a meaningful impact on the simulation of the Carbon isotopic fields.

Also added a general test for this and specific one to catch this case.

Contributors other than yourself, if any: @klindsey, @olyson @dlawren @billsacks @bishtgautam

CTSM Issues Fixed (include github issue #):

Fixes #675
Fixes #686

Are answers expected to change (and if so in what way)? Yes

Answers change quantitatively (but not qualitatively) for bulk Carbon when use_c13 or use_c14 is on, but C13 and C14 is wrong over areas with land-use change after the years boundary happens. The effect is especially strong with soil Carbon.

Any User Interface Changes (namelist or namelist defaults changes)? No

Testing performed, if any: standard testing on cheyenne

http://webext.cgd.ucar.edu/I20TR/clm50_release-clm5.0.20_1deg_GSWP3V1_isofix2_hist/lnd/clm50_release-clm5.0.20_1deg_GSWP3V1_isofix2_hist.1995_2014-clm50_release-clm5.0.20_1deg_GSWP3V1_isofix_hist.1995_2014/setsIndex.html

@ekluzek ekluzek added type: bug - impacts science priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations branch tag: release Changes go on release branch as well as master labels Apr 26, 2019
@ekluzek ekluzek added this to the cesm2.1.1 milestone Apr 26, 2019
@ekluzek ekluzek self-assigned this Apr 26, 2019
@ekluzek ekluzek merged commit de130a3 into ESCOMP:release-clm5.0 May 8, 2019
@ekluzek ekluzek deleted the relcisofix branch May 8, 2019 19:33
AGonzalezNicolas pushed a commit to HPSCTerrSys/clm5_0 that referenced this pull request Jun 27, 2024
Bring the carbon isotope fix to the release branch
AGonzalezNicolas pushed a commit to HPSCTerrSys/clm5_0 that referenced this pull request Jul 5, 2024
Bring the carbon isotope fix to the release branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch tag: release Changes go on release branch as well as master priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant