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

Update for WW3 initialization #2585

Closed

Conversation

JessicaMeixner-NOAA
Copy link
Collaborator

Commit Queue Requirements:

  • Fill out all sections of this template.
  • All sub component pull requests have been reviewed by their code managers.
  • Run the full Intel+GNU RT suite (compared to current baselines) on either Hera/Derecho/Hercules
  • Commit 'test_changes.list' from previous step

Description:

When using PIO restarts, we needed to add a capability to read binary restarts when using runtype=intial. For example, this is used in the high resolution (HR) experiments.

Commit Message:

Update for WW3 initialization

* UFSWM - 
  * WW3 -  Updated hash for WW3 initialization 

Priority:

  • Critical Bugfix: Reason
  • High: Reason
  • Normal

Git Tracking

UFSWM:

Sub component Pull Requests:

UFSWM Blocking Dependencies:

  • None

Changes

Regression Test Changes (Please commit test_changes.list):

  • No Baseline Changes.

Input data Changes:

  • None.

Library Changes/Upgrades:

  • No Updates

Testing Log:

  • RDHPCS
    • Hera
    • Orion
    • Hercules
    • Jet
    • GaeaC5
    • GaeaC6
    • Derecho
  • WCOSS2
    • Dogwood/Cactus
    • Acorn
  • CI
  • opnReqTest (complete task if unnecessary)

@DeniseWorthen
Copy link
Collaborator

@JessicaMeixner-NOAA Since I don't think any RT will cover this case, have you tested this feature to ensure possible failures have been captured? For example, in an RT sandbox by requesting a binary restart for an initial run but not having one present, or having one with the wrong name, etc.

@JessicaMeixner-NOAA
Copy link
Collaborator Author

@DeniseWorthen I have tested this within the global-workflow low resolution test ci test case and ensured that the significant wave height was non-zero at forecast hour 0. The global-workflow clone is here (note I only changed my branch of WW3, I didn't have this ufs-waether-model PR yet+ it's a branch of g-w): /scratch1/NCEPDEV/climate/Jessica.Meixner/UpdateFixandHiresIC/global-workflow and my output of the test is here: /scratch1/NCEPDEV/climate/Jessica.Meixner/UpdateFixandHiresIC/c48t05

I'm going to submit a higer-res case from the global-workflow that doesn't have just an initial IC to triple check things now.

@JessicaMeixner-NOAA
Copy link
Collaborator Author

@DeniseWorthen - Additional sanity check from g-w with a C768 HR like set-up can be found here: /scratch1/NCEPDEV/climate/Jessica.Meixner/UpdateFixandHiresIC/c768t02/COMROOT/c768t02/gfs.20191203/00/products/wave/gridded/global.0p25 and the f000:

Screenshot from 2025-01-31 16-37-43

@DeniseWorthen
Copy link
Collaborator

@JessicaMeixner-NOAA Thanks. I wasn't really concerned about the validity of starting from binary, rather that the option worked correctly w/ your code changes---that if run = initial and the binary file was not present, it would abort for example. This isn't something we would test for in the RTs, so I just wanted to be sure you had tested out various scenarios for how this could not do what you expected it to do.

@JessicaMeixner-NOAA
Copy link
Collaborator Author

I have not tested that @DeniseWorthen - I can't test that from the workflow, because I have it designed to not get to that scenario. I'd have to either change the workflow to force this or find an rt.sh test that has these cases. I was more concerned that it actually read the IC.

@JessicaMeixner-NOAA
Copy link
Collaborator Author

Have confirmed we get the correct error if not binary WW3 restart exists:

Test directory:
/scratch1/NCEPDEV/stmp2/Jessica.Meixner/FV3_RT/rt_1730975/cpld_control_gfsv17_intel_testfail
Error: /scratch1/NCEPDEV/stmp2/Jessica.Meixner/FV3_RT/rt_1730975/cpld_control_gfsv17_intel_testfail/err

Error message:
197: WW3 ERROR: required restart file ufs.cpld.ww3.r.2021-03-22-21600 does not exist

@DeniseWorthen
Copy link
Collaborator

Great. Thanks for verifying that it fails as expected.

@dpsarmie
Copy link
Collaborator

dpsarmie commented Feb 3, 2025

@JessicaMeixner-NOAA Jong wanted to combine PRs so I brought in these changes into PR #2587 . Looked good from my end but feel free to look it over when you have a chance to double-check that the correct changes were brought in. Thanks

@JessicaMeixner-NOAA
Copy link
Collaborator Author

Changes look correctly added to me @dpsarmie

jkbk2004 pushed a commit that referenced this pull request Feb 5, 2025
…ations // #2585 Update for WW3 initialization (#2587)

* UFSWM - Add Land IAU variables to default_vars and allow control_c48_lnd_iau to run using the global_control.nml.IN template.
   * WW3 -  Updated hash for WW3 initialization  (#2585)

---------

Co-authored-by: Jessica Meixner <[email protected]>
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.

WW3 ICs to be read when using PIO & runtype=intiial
3 participants