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

Some soil decomposition history fields have the pool number rather than a description in their name #1392

Closed
ekluzek opened this issue Jun 3, 2021 · 5 comments · Fixed by #1413
Assignees
Labels
enhancement new capability or improved behavior of existing capability

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Jun 3, 2021

This is a change in ctsm5.1.dev043. Some soil decomposition history fields now have the pool number in their name rather than description. Previously they had LIT, CEL, or MET in the name and now they have a number 1,2, or 3. I think it will be easier for people to have the description in the name rather than a number where they have to examine the code to figure out which pool it refers to.

These fields are default inactive:

DWT_FROOTN_TO_LITR_N
C13_DWT_FROOTC_TO_LITR
C
C14_DWT_FROOTC_TO_LITR
*_C

@wwieder

@ekluzek ekluzek added enhancement new capability or improved behavior of existing capability next this should get some attention in the next week or two. Normally each Thursday SE meeting. labels Jun 3, 2021
@ekluzek
Copy link
Collaborator Author

ekluzek commented Jun 3, 2021

I also wonder if we should add some tests that output these fields.

@billsacks billsacks removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Jun 10, 2021
@wwieder
Copy link
Contributor

wwieder commented Jun 10, 2021

@slevisconsulting let's talk about this after the CESM workshop. This is related to concerns @ekluzek raised about readability of the code. Maybe we can just add long names that are more descriptive for each model (e.g. when to define lit-met vs. lit-struc for mimcs vs. lit-met, lit-cel, lit-lig for century)? Similarly soils should be 'available', 'chemically protected' and 'physically protected' in mimics vs. active, slow & passive for century

@wwieder
Copy link
Contributor

wwieder commented Jun 23, 2021

@ekluzek I understand you concern but have two thoughts in advance of our call.

Currently the soil model uses numbering for LIT and SOIL pools

decomp_cascade_con%decomp_pool_name_restart(i_met_lit) = 'litr1'

can MIMICS use the same approach here, by defining LIT_1 as METABOLIC and LIT_2 as STRUCTURAL, but then just using the numbered pools in the code? Maybe I'm not completely understanding your concern?

@ekluzek
Copy link
Collaborator Author

ekluzek commented Jun 23, 2021

Yes, I am just talking about the name on the history files, and NOT what's in the code. The code would continue to have it as a numbered pool, but the name of the history variable would include the pool description (so you don't have to look up the meaning of each numbered pool). The idea is to just make this easier for scientists who are running the model and looking at the history fields.

In our discussion you suggested using a short descriptor of 3 or 4 characters, and just have it longer in the long_name.

@wwieder
Copy link
Contributor

wwieder commented Jun 23, 2021

@ekluzek and I talked more about this and I agree with him that on the name on history fields would be more instructive and helpful for scientists looking at output.

For the current BGC these should be:

  • LIT_MET_C, LIT_CEL_C, and LIT_LIG_C that correspond to litter carbon in metabolic, cellulose, and lignin pools (with parallel pools for N). then for soils:
  • SOIL_FAST_C, SOIL_SLOW_C, SOIL_PASS_C for active, slow and passive soil C pools. I'm happy with any abbreviations, underscores, etc that keep this consistent with CTSM naming conventions

Second, as it would be fine to bring this in with #1400, but the CWD work is important for the PPE branch and should be prioritized. This can go in with another bfb tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability
Projects
None yet
4 participants