Skip to content

Add some biophysical variables by land-use type#1407

Open
ckoven wants to merge 5 commits intoNGEET:mainfrom
ckoven:landuse_biophys_histvars2
Open

Add some biophysical variables by land-use type#1407
ckoven wants to merge 5 commits intoNGEET:mainfrom
ckoven:landuse_biophys_histvars2

Conversation

@ckoven
Copy link
Contributor

@ckoven ckoven commented May 12, 2025

In order to look at biophysical effects of land use, it's useful to have a small number of relevant variables indexed by land use type. This PR allows that, so that you can look at: vegetation temperature, surface air temperature, and a basic set of energy fluxes (SW, LW, SH, LH) separately for each land use type. I.e., they are output on the fates_levlanduse history dimension for each gridcell.

This requires HLM-side logic. I have a commit on E3SM that handles this at ckoven/E3SM@5fd137b (PR forthcoming)

Currently these are all output when the hi frequency history flag is set to 1; in principle this should actually be when the flag is set to 2, so that should probably change before bringing this PR in. (for the purpose of the experiments I am currently running, I want these and only these subgridscale high-frequency variables though.)

Also, the logic that averages in bare-ground-patch properties will only work for nocomp configurations. Further work is needed to be correct for full-FATES configurations as well, but I got lost in how to index a given site's bare-ground patch when nocomp isn't on, so I need to come back to that.

Also, the patch-weighting logic for these variables is slightly different than for other patch-level variables (e.g., the `fates_levage' -indexed ones). This is for two reasons: (1) we need to average in some of the bare ground patch properties to weight things correctly, because the FATES and HLM patch areas mean different things, and (2) the land use areas are less generally dynamic than the age binned logic, and so there is less chance of weirdness when the averaging denominator changes abruptly. So the upshot is that less postprocessing is needed for these (i.e they are simpler to work with), but also that they might not sum perfectly to the total site values because of changing denominators over time.

Description:

fixes #1404.

Collaborators:

discussed with @glemieux, @rgknox, @aswann

Expectation of Answer Changes:

This only adds new diagnostic variables, so should be bit for bit otherwise.

Checklist

If this is your first time contributing, please read the CONTRIBUTING document.

All checklist items must be checked to enable merging this pull request:

Contributor

  • The in-code documentation has been updated with descriptive comments
  • The documentation has been assessed to determine if updates are necessary

Integrator

  • FATES PASS/FAIL regression tests were run
  • Evaluation of test results for answer changes was performed and results provided
  • FATES-CLM6 Code Freeze: satellite phenology regression tests are b4b

If satellite phenology regressions are not b4b, please hold merge and notify the FATES development team.

Documentation

Test Results:

CTSM (or) E3SM (specify which) test hash-tag:

CTSM (or) E3SM (specify which) baseline hash-tag:

FATES baseline hash-tag:

Test Output:

Copy link
Contributor

@samsrabin samsrabin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, Charlie! Just a few suggestions.

Also, a question: I'm having trouble understanding why and under what circumstances these should fail to sum to the site value. Could you explain that in a bit more detail?

@github-project-automation github-project-automation bot moved this from Finding Reviewers to Under Review in FATES Pull Request Planning and Status May 13, 2025
@glemieux
Copy link
Contributor

glemieux commented Jun 5, 2025

@ckoven where is this on the priority queue for the CLM6 code freeze?

@glemieux glemieux added the software: API Pertaining to specific API updates with any host land model label Aug 22, 2025
@ckoven
Copy link
Contributor Author

ckoven commented Oct 10, 2025

added E3SM PR for this: E3SM-Project/E3SM#7783

@glemieux glemieux self-requested a review October 13, 2025 19:16
@rgknox rgknox self-requested a review November 3, 2025 20:26
@glemieux
Copy link
Contributor

glemieux commented Feb 9, 2026

@samsrabin would you confirm that your suggestions have been resolved and approve this if so?

@samsrabin
Copy link
Contributor

GitHub PRs are seemingly having a bad day, so I'll work on this tomorrow.

@samsrabin samsrabin self-requested a review February 10, 2026 17:16
Copy link
Contributor

@samsrabin samsrabin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks!

! ===============================================================================================


subroutine update_history_hifrq_landuse(this,nc,nsites,sites,bc_in,dt_tstep)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Linking @rgknox comment here update_history_hifrq_landuse due to closing #1529

Comment on lines +5427 to +5429
cpatch => sites(s)%oldest_patch
do while(associated(cpatch))
if (cpatch%total_canopy_area .gt. rsnbl_math_prec) then
Copy link
Contributor

@glemieux glemieux Feb 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copying @rgknox question here from #1529 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

science: land use Pertaining to land use software: API Pertaining to specific API updates with any host land model software: history output Pertaining to FATES history output variables type: enhancement

Projects

Status: Under Review

Development

Successfully merging this pull request may close these issues.

Biophysical variables by land use type?

3 participants