Skip to content

radiation refactors - rad_error and rad profile diagnostics#1397

Merged
rgknox merged 7 commits intoNGEET:mainfrom
rgknox:trivial-zenith-defaults-raderrorfix
Oct 13, 2025
Merged

radiation refactors - rad_error and rad profile diagnostics#1397
rgknox merged 7 commits intoNGEET:mainfrom
rgknox:trivial-zenith-defaults-raderrorfix

Conversation

@rgknox
Copy link
Contributor

@rgknox rgknox commented Apr 24, 2025

Description:

This set of changes addresses isues brought up by @mvdebolskiy related to coupling radiation with FATES and CAM: #1376 (comment) . This led to a generalized refactor of radiation diagnostics, particularly radiation profiles, and how these things are initialized and written to output given the nature of the normalized radiation calls (ie that the current day's albedo is calculated at the end of the previous timestep).

This PR has a sibling PR in NorESMhub: https://github.com/NorESMhub/fates/pull/17/files

Collaborators:

@mvdebolskiy

Expectation of Answer Changes:

yes, this will change fates radiation history variables (high frequency multi-layer canopy output), but those only. This is because more attention is being paid to when they are zero'd and when they are ignored.

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:

@rgknox rgknox added the status: Not Ready The author is signaling that this PR is a work in progress and not ready for integration. label Apr 24, 2025
@rgknox
Copy link
Contributor Author

rgknox commented Jun 9, 2025

See comment: ESCOMP/CTSM#3051 (comment)

cc @mvdebolskiy

@glemieux glemieux moved this from Finding Reviewers to Stuck in FATES Pull Request Planning and Status Jul 28, 2025
@glemieux glemieux moved this from Stuck to Under Review in FATES Pull Request Planning and Status Aug 25, 2025
@rgknox rgknox removed the status: Not Ready The author is signaling that this PR is a work in progress and not ready for integration. label Sep 15, 2025
@glemieux glemieux self-requested a review September 15, 2025 18:43
Copy link
Contributor

@glemieux glemieux left a comment

Choose a reason for hiding this comment

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

This looks good. I really like how the downstream calculations for the diagnostics are now conducted in the history interface module. I like the practice of adjusting the output in this module, rather than in the calculating module.

@rgknox
Copy link
Contributor Author

rgknox commented Oct 13, 2025

All tests ok on Derecho, compared against base: fates-sci.1.87.3_api.41.0.0-ctsm5.3.077

Some expected diffs with base, but relegated to only the variables that were changed (rad_error and some of the multiplexed rad diagnostics).

Also, I was hoping that this test would start passing, and it does!

PASS ERI_D_Ld9.f45_f45_mg37.I2000Clm60FatesSpCruRsGs.derecho_gnu.clm-FatesColdSatPhenCamLndTuningMode COMPARE_base_rest (UNEXPECTED: expected FAIL)

@rgknox rgknox merged commit 906d03b into NGEET:main Oct 13, 2025
1 check passed
@github-project-automation github-project-automation bot moved this from Final Testing to Ready to Integrate in FATES Pull Request Planning and Status Oct 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants