Skip to content

Fix GFSv17 Restart IAU Reproducibility by Adjusting WW3 Internal Timestep#2784

Closed
mingchen-NOAA wants to merge 7 commits into
ufs-community:developfrom
mingchen-NOAA:ufs_gfsv17_restart_iau
Closed

Fix GFSv17 Restart IAU Reproducibility by Adjusting WW3 Internal Timestep#2784
mingchen-NOAA wants to merge 7 commits into
ufs-community:developfrom
mingchen-NOAA:ufs_gfsv17_restart_iau

Conversation

@mingchen-NOAA
Copy link
Copy Markdown
Collaborator

@mingchen-NOAA mingchen-NOAA commented Jun 23, 2025

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:

This pull request resolves the GFSv17 restart IAU reproducibility issue by modifying the WW3 internal timestep in ww3_grid.inp.exp.global_270k from 720. 360. 360. 30. to 900. 450. 450. 30. to ensure the ITIME parameter is consistent between control and restart runs. The WW3 input files were regenerated accordingly. A new test configuration file tests/tests/cpld_restart_gfsv17_iau was added, and tests/rt.conf was updated to include this restart IAU test case while removing the GFSv17 no wave test cases. Additionally, tests/fv3_conf/cpld_control_run.IN was modified to address an issue with creating the pnt_wght.ww3.nc file for the restart IAU test, and tests/rt.sh was updated to point to the newly created input directory.

The new input directory on Hera:
/scratch4/NCEPDEV/marine/Ming.Chen/ufs_iau_timefix/WW3_input_data_20250715

A full rt tests were conducted and following changes were found due to change the input timesteps.

cpld_control_gfsv17 intel
cpld_control_gfsv17_iau intel
cpld_restart_gfsv17 intel
cpld_restart_gfsv17_iau intel
cpld_mpi_gfsv17 intel
cpld_control_sfs intel
cpld_debug_gfsv17 intel

Commit Message:

* UFSWM - Updated WW3 timestep input and created cpld_restart_gfsv17_iau test case

Priority:

  • Normal

Git Tracking

UFSWM:

Sub component Pull Requests:

  • None

UFSWM Blocking Dependencies:

  • None

Documentation:

  • This PR requires a documentation update, and the WM User's Guide has been updated based on the changes in this PR.
  • This PR requires a documentation update, and a WM issue has been opened to track the need for a documentation update; a person responsible for submitting the update has been assigned to the issue (link issue).
  • No documentation update is required for this PR (please explain).

Changes

Regression Test Changes (Please commit test_changes.list):

  • PR Adds New Tests/Baselines.
  • PR Updates/Changes Baselines.

Input data Changes:

/scratch4/NCEPDEV/marine/Ming.Chen/ufs_iau_timefix/WW3_input_data_20250715

Library Changes/Upgrades:

  • No Updates

Testing Log:

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

@junwang-noaa junwang-noaa mentioned this pull request Jul 3, 2025
14 tasks
@DeniseWorthen DeniseWorthen added Baseline Updates Current baselines will be updated. Changes Existing Input Data Existing input data will be changed. A new input-data-YYYYMMDD directory must be created. labels Jul 14, 2025
@DeniseWorthen
Copy link
Copy Markdown
Collaborator

@mingchen-NOAA Please add a Hera location where the new WW3 input-data can be found, it will be sync'd from that location to all RDHPCS.

Also, if older WW3-input-data can be removed, it might be a good time to clean them up (?). Currently we're retaining input from 2022 and 2024.

WW3_input_data_20220624
WW3_input_data_20240214
WW3_input_data_20250114
WW3_input_data_20250212
WW3_input_data_20250225

@mingchen-NOAA
Copy link
Copy Markdown
Collaborator Author

The input data for this fix on Hera is defined in the modified rt.sh script (changes in rt.sh) or
/scratch2/NCEPDEV/marine/Ming.Chen/ufs-weather-model/ufs_IAU/ufs_iau_timefix/ww3_input_timefix

I will check input data and remove the unused old files. Thank you!

Comment thread tests/rt.conf Outdated
RUN | cpld_mpi_gfsv17 | - noaacloud | |
RUN | cpld_control_gfsv17_nowav_iau | - noaacloud | baseline | cpld_control_gfsv17
RUN | cpld_restart_gfsv17_nowav_iau | - noaacloud | | cpld_control_gfsv17_nowav_iau
#RUN | cpld_control_gfsv17_nowav_iau | - noaacloud | baseline | cpld_control_gfsv17
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I believe the expectation is that the nowav_iau tests would be removed.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Yes. We will remove the no-wave tests b/c we have created a cpld_restart_gfsv17_iau test.

Copy link
Copy Markdown
Collaborator

@DeniseWorthen DeniseWorthen Jul 14, 2025

Choose a reason for hiding this comment

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

But shouldn't both the actual tests be removed and the rt.conf fixed?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I will fix the rt.conf. Thanks!

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Now I remove nowav_iau tests from rt.conf. Thank you!

@DeniseWorthen
Copy link
Copy Markdown
Collaborator

@mingchen-NOAA Could you add the new input-data path (to make it explicit for the EPIC CMs) to the PR information? Thanks!

@mingchen-NOAA
Copy link
Copy Markdown
Collaborator Author

Yes. I will fix it with the input path.

@DeniseWorthen
Copy link
Copy Markdown
Collaborator

@mingchen-NOAA The same itime bug is the reason that the current ultralow configurations do not restart reproduce. See #2652. I would like to include the fix in this PR if you would agree. It would mean

  1. updating mod_def.uglo_900km. I've tested timesteps 1800. 900. 900. 30. and 1800. 1800. 1800. 30. and both give restart repro.
  2. uncommenting the LIST_FILES in the ultralow restart tests.
  3. retesting; all the ultralow configs will then require new baselines in addition to the IAU tests.

If you agree, I can prepare a PR which you can merge w/ your existing UWM PR.

@mingchen-NOAA
Copy link
Copy Markdown
Collaborator Author

I’m currently preparing a code fix PR to address this issue as a long-term solution, so that input changes won’t be necessary. I plan to submit the new PR today. If you think it would be more efficient, we can combine this with the updates you’ve outlined so they are included in a single PR.

@DeniseWorthen
Copy link
Copy Markdown
Collaborator

@mingchen-NOAA Thanks. So do you intend to use this PR (with the timestep change) or close this and create a new one?

@mingchen-NOAA
Copy link
Copy Markdown
Collaborator Author

I prefer to create a new one. Could you prepare a PR so I can merge it and test it together with my code fix? We can start from there. Sounds good?

@DeniseWorthen
Copy link
Copy Markdown
Collaborator

OK, sounds good. I knew you'd need a WW3 update, so I figured you would be creating a new one. I'll create one and tag it here. Thanks.

@mingchen-NOAA
Copy link
Copy Markdown
Collaborator Author

Or, you can point me to your branch with the test configurations so I can run the tests directly.

@DeniseWorthen
Copy link
Copy Markdown
Collaborator

@mingchen-NOAA
Copy link
Copy Markdown
Collaborator Author

Thank you! I will test it with my code fix.

@DeniseWorthen
Copy link
Copy Markdown
Collaborator

Oh shoot. No, that won't work because we can't alter an existing input-data directory. We can add new input, but we cannot change existing input. (For WW3, we just create a new sub-directory but that is the only case where we carry a separate input-data.)

I was trying to avoid new input-data in this go-around, since I want to do the new input-data directory once we have the V2 bug in the ATM restarts fixed; that will come in with my SFS C192mx025 test update and who knows how many weeks it will be before that gets to the top of the Q.

Could we just fix the ultralow tests for now by modifying the mod_def? These tests run so fast, I don't think it matters much if we make WW3 take a little longer.

@mingchen-NOAA
Copy link
Copy Markdown
Collaborator Author

No worries. I fixed my code to separate the write and read control parameter so for the warmstart cases, I can make it write only.

@dpsarmie
Copy link
Copy Markdown
Collaborator

@mingchen-NOAA Is this PR still needed or will #2851 replace this PR?
#2851 is scheduled to be next in the commit queue and I wanted to double-check on this PR.

@mingchen-NOAA
Copy link
Copy Markdown
Collaborator Author

mingchen-NOAA commented Aug 18, 2025

#2851 replaces this one. Thank you for checking!

@dpsarmie
Copy link
Copy Markdown
Collaborator

Ok then I will close this PR for now. If you need to reopen it, feel free to do so.

@dpsarmie dpsarmie closed this Aug 18, 2025
@mingchen-NOAA
Copy link
Copy Markdown
Collaborator Author

Thank you very much!

@mingchen-NOAA mingchen-NOAA deleted the ufs_gfsv17_restart_iau branch November 21, 2025 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Baseline Updates Current baselines will be updated. Changes Existing Input Data Existing input data will be changed. A new input-data-YYYYMMDD directory must be created.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants