Skip to content

Conversation

@chengzhuzhang
Copy link
Collaborator

@chengzhuzhang chengzhuzhang commented Aug 18, 2025

Summary

The original design assumption was that ref_years and years would have the same number
of year sets, creating 1:1 pairings:

  • Test period 1 vs Reference period 1
  • Test period 2 vs Reference period 2
  • etc.

One of the common use cases include single reference : ref_years = "451-500" with multiple test periods. This fix handles this common us case while keep the original design.

Select one: This pull request is...

  • a bug fix: increment the patch version
  • a small improvement: increment the minor version
  • a new feature: increment the minor version
  • an incompatible (non-backwards compatible) API change: increment the major version

Small Change

  • To merge, I will use "Squash and merge". That is, this change should be a single commit.
  • Logic: I have visually inspected the entire pull request myself.
  • Pre-commit checks: All the pre-commits checks have passed.

@forsyth2
Copy link
Collaborator

Thanks @chengzhuzhang. If you've tested this on some relevant data sets, I can approve to merge.

@chengzhuzhang
Copy link
Collaborator Author

Yes, I tested with a recent run on v3.HR. I think it is okay to merge.

@chengzhuzhang chengzhuzhang requested a review from forsyth2 August 18, 2025 20:01
@forsyth2 forsyth2 merged commit c0ea3f9 into main Aug 18, 2025
4 checks passed
@forsyth2 forsyth2 deleted the fix-e3sm-diags-year-loop-land branch August 18, 2025 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants