Skip to content

Fix geostrophic wind forcing using UFS_case_gen#644

Draft
grantfirl wants to merge 1 commit intoNCAR:mainfrom
grantfirl:geostrophic_forcing_testing
Draft

Fix geostrophic wind forcing using UFS_case_gen#644
grantfirl wants to merge 1 commit intoNCAR:mainfrom
grantfirl:geostrophic_forcing_testing

Conversation

@grantfirl
Copy link
Collaborator

SOURCE: @grantfirl

DESCRIPTION OF CHANGES:

  • Bullet points or paragraphs describing problem, solution, and required changes.
  • Update documentation under scm/doc if needed.

ISSUE: # Enter GitHub Issue number after #

ASSOCIATED PRs:

  • NCAR/ccpp-physics#
  • NCAR/ccpp-framework#

TESTS CONDUCTED: List tests done as appropriate. Delete if not used.

This PR catches the NCAR:main branch up with changes from the ufs-community:ufs/dev branch.

Associated ufs/dev PR:

  • ufs-community/ccpp-physics#

Associated ufsatm PR:

  • NOAA-EMC/ufsatm#

Associated NCAR PR:

  • NCAR/ccpp-physics#

REGRESSION TEST CHANGES: Enter NONE if not applicable. Otherwise, expected results changes, input data changes, changes to the software, etc.

…e; calculate geopotential differently; calculate geostrophic wind differently
@hertneky
Copy link
Collaborator

@grantfirl Here are some plots of aggregated T, Qv, U, V. Similar to ones done in preparation for v7 release. I am realizing that our previous tests used RTs that were 3-hourly, which might affect the results. I used the RTs used in the case_gen CI that have 12hr history files. Are there RTs somewhere that have 3-hr output?
case_gen_jan122026.pdf

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.

2 participants