-
Notifications
You must be signed in to change notification settings - Fork 317
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
Soil gas diffusivity bugfix #2157
Soil gas diffusivity bugfix #2157
Conversation
FATES API update to facilitate fates refactor This updates a number of FATES type names and module use statements which correspond with a refactoring effort that moves FATES patches and cohorts into their own respective modules. With the FATES update is a minor science update, so there are changes to answers for FATES. This also incorporates a minor update to a more recent version of the ccs config external. # Conflicts: # doc/source/users_guide/setting-up-and-running-a-case/master_list_nofates.rst
@jinmuluo Would you mind having a look at the changes here to make sure they all look good? |
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.
Have you run tests to evaluate the impact of this bug fix on fluxes simulated in the model?
@wwieder If you're asking about scientific tests of the impact, no, I haven't. I do have all the (Cheyenne) aux_clm outputs, though, so we could look at those. |
I think it's worth running a longer case to understand the scientific impacts on the bug fix, or is the answer changing part of this just due to roundoff changes in the order of operations? |
A longer test makes sense, @wwieder, since the diffs aren't just roundoff-level. How long do you think, and at what resolution? |
My default is for a full spinup from cold start and then historical simulation at 1 degree, but lately we've been testing things out more with the sparse grid from the PPE. What do you think @slevis-lmwg, @dlawrenncar and @linniahawkins? |
@wwieder I don't have first-hand experience with the PPE sparse grid; however, it seems like a reasonable time-saving approach to use it. |
Thanks, @linniahawkins! @wwieder, looks good to me; what do you think? |
Sorry, what are you asking here, @samsrabin? If it's OK to evaluate effects of the bug fix on ecosystem states and fluxes using the sparse grid instead of a full global simulation? I think this seems like a reasonable way to quantify the magnitude of the bug fix. Or at least to try... My question more on the process side of things, (e.g. how to we understand / quantify answer changing tags & can we leverage the sparse grid)? I don't think we can use the PPE branch tag here, as it's not up to date with main, but you still should be able to use the sparse grid surface dataset. At some point I'd be curious to have a closer look at differences between Daniel's extrapolation from the 400 points back to the globe and a gridded simulation, but that's not really the question here. |
Marking as blocked because I want to run with the PPE sparse grid, but sparse grids are incompatible with NUOPC. |
Just so I understand fully, are sparse grids completely incompatible with
NUOPC or just incompatible at the moment until someone resolves the issue?
…On Wed, Oct 4, 2023 at 3:20 PM Sam Rabin ***@***.***> wrote:
Marking as blocked because I want to run with the PPE sparse grid, but
sparse grids are incompatible with NUOPC.
—
Reply to this email directly, view it on GitHub
<#2157 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFABYVGFRVWN6DCL4IGOHULX5XHJDAVCNFSM6AAAAAA4XOEEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBXGY2TQNRRGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@dlawrenncar Just for now. @adrifoster, @slevis-lmwg, and @ekluzek are working on adding the capability. |
@dlawrenncar see #1731 to see where we are at in the process. I did get a test case working with an earlier version of this. But, we didn't bring it in as something that we test. And since that time mesh_modifier was completed and will be the way we make the process replicatable. Once, @adrifoster has this working, we will save it as a user-mod directory and start testing with it. And we will update the notes on the process to make sure we have a process that can be replicated. @adrifoster also found a file in the PPE work that we can base these files off of. |
Generally speaking, it works, e.g. Xiulin's work with Charlie and Lara. |
b4b changes to Python scripts, history lists, tech note, and clm_time_manager. * Add system and unit tests for making fsurdat with all crops everywhere (ESCOMP#2081) * Rework master_list* files etc. (ESCOMP#2087) * Fixes to methane Tech Note (ESCOMP#2091) * Add is_doy_in_interval() function (ESCOMP#2158) * Avoid using subprocess.run() in FSURDATMODIFYCTSM (ESCOMP#2125) Closes issues: * Add unit test for making fsurdat with all crops everywhere (ESCOMP#2079) * Rework master_list_(no)?fates.rst? (ESCOMP#2083) * conda run -n can fail if a conda environment is already active (ESCOMP#2109) * conda fails to load for SystemTests (ESCOMP#2111)
I'll go ahead and test with a 4x5 grid instead of waiting for the NUOPC sparse grid. |
It looks like this results in a reduction of mean global diffusivity by about 12.7%: This ranges from about 0–35% across gridcells in two years I looked at: @wwieder Because of how quickly diffusivity levels out, it doesn't seem necessary to do another run but from a spinup with the fix applied. What do you think? |
I agree, seems like a pretty minor difference. What do trace gas fluxes
look like (CO2, CH4, Denitrif, or N2O)? I'm assuming they also aren't
large and this can be merged.
…On Thu, Oct 26, 2023 at 2:53 PM Sam Rabin ***@***.***> wrote:
It looks like this results in a reduction of mean global diffusivity by
about 12.7%:
[image: screenshot_6517]
<https://user-images.githubusercontent.com/10454527/278472601-eddbc414-1f5b-4c01-92ff-e8e356639eba.png>
This ranges from about 0–35% across gridcells in two years I looked at:
[image: screenshot_6518]
<https://user-images.githubusercontent.com/10454527/278472796-303dbcd8-0920-46eb-a8df-c0dcf0f08407.png>
@wwieder <https://github.com/wwieder> Because of how quickly diffusivity
levels out, it doesn't seem necessary to do another run but from a spinup
with the fix applied. What do you think?
—
Reply to this email directly, view it on GitHub
<#2157 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5IWJC44WBMA6FLKLR5A4TYBLEWHAVCNFSM6AAAAAA4XOEEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRHA4DAMRUG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Great. I think this is good to merge. Thanks, Sam. |
Hi Sam,
I've seen the same changes in my outputs.
Best,
will wieder ***@***.***> 于2023年10月26日周四 19:57写道:
… Great. I think this is good to merge. Thanks, Sam.
—
Reply to this email directly, view it on GitHub
<#2157 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK7DGCRAVOOGRTFZGRUER6LYBL2E5AVCNFSM6AAAAAA4XOEEZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBSGA4DQMJVGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Description of changes
Resolves two bugs in the calculation of diffusion in
SoilBiogeochemNitrifDenitrif()
. Also does some rearranging and renaming to improve clarity.Specific notes
From #1990:
Contributors other than yourself, if any: @jinmuluo, @wwieder
CTSM Issues Fixed:
Are answers expected to change (and if so in what way)? Yes. Of outputs in aux_clm tests, only
F_N2O_DENIT
is affected.Any User Interface Changes (namelist or namelist defaults changes)? No.
Testing performed:
aux_clm:
ctsm5.1.dev133
only in history fieldF_N2O_DENIT
. (At least on Cheyenne; my Izumi test has been wiped. Can rerun if needed.)F_N2O_DENIT
.