Enable running regional nesting configurations and add four regional and global nesting RTs as well as two HAFS WW3 coupling RTs#846
Conversation
- hafs_regional_1nest_atm - hafs_regional_telescopic_2nests_atm - hafs_global_1nest_atm - hafs_global_multiple_4nests_atm * Unify and simplify the existing HAFS regression tests for both scripts and input data.
0a4bb7a to
98fc596
Compare
…c files for the hafs_regional_1nest_atm RT to speed up the write grid component.
…_hafs.nml.IN. *Change FHCYC from 24 to 0 for hafs RTs.
- hafs_regional_atm_wav: two-way atm-wav coupling - hafs_regional_atm_ocn_wav: two-way atm-ocn coupling and one-way atm2wav coupling
…directories on orion
9d22bc9 to
5738871
Compare
…N and tests/fv3_conf/hafs_ww3_run.IN.
|
I have synced up with the latest develop branch. Appreciate it if someone can help stage (transfer) the following new updated input data directory from Orion: |
@junwang-noaa, I looked at this hafs_global_multiple_4nests_atm RT on your wcoss_cray dir, the different nan values are probably partly related to the fact the output grid specified in this test case does not overlap with the first nested domain. This will not be the issue in the future, once we can write output grid for all the nested grids. So, I would suggest to just turn off this hafs_global_multiple_4nests_atm RT on wcoss_cray for now. I can try to fix this for the future PR when adding the HAFS debug/threading RTs if that sounds good to you as well. |
|
@BinLiu-NOAA I checked with the code managers. Since you will work on fixing the issues, it is OK to turn off the 4 HAFS test on jet and the hafs_global_multiple_4nests_atm test on cray. Please create an issue on ufs-weather-model repo on fixing those tests. Meanwhile please update your branch, we will finish the RT on jet and cray with the updated rt.conf, then commit the code after review. Thanks |
…ce they run out of wallclock limit. *Turn off the hafs_global_multiple_4nests_atm RT on wcoss_cray, since the rerun cannot bitwisely reproduce the baseline for the atmf006.nc file. This is partly due to the fact the output grid domain specified for the write grid component is not overlapped by nest02 (inside tile 2), but by nest03-05 inside tile 6. Note: The above issues will be worked on and fixed in a follow-up PR.
Thanks, @junwang-noaa! I have made the following changes accordingly:
And I will create the corresponding issues for these and will fix them in a follow-up PR when adding the HAFS related debug RTs. Thanks! |
|
Automated RT Failure Notification |
@junwang-noaa or @BrianCurtis-NOAA, I could not see any useful out/err info for these two failed tests. I copied over the two failed test run dirs and tried them from my own side through submitting the job_cards. And the two tests is currently running fine on Jet now: Bin |
|
Automated RT Failure Notification |
|
@BinLiu-NOAA the Cray log file is at: |
@junwang-noaa, Hera is down for maintenance now. Could you please commit the wcoss_cray log directly from wcoss_cray back to this feature/regional_nest branch (you should already have write access to this feature branch)? Or you can point me directly to your wcoss_cray dir. Thanks! Bin |
|
@BinLiu-NOAA I still can't commit to your branch. The cray log file is at: |
RT log for wcoss_cray now is also updated. |
DeniseWorthen
left a comment
There was a problem hiding this comment.
Thanks for removing the edit_inputs and switching everything to atparse.
@JessicaMeixner-NOAA helped to remove edit_inputs and unified to use atparse for ww3_multi.inp.IN for all WW3 related RTs. Thanks! |
|
Thanks, @JessicaMeixner-NOAA ! |
Done! Thanks! |
PR Checklist
Ths PR is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR. Please consult the ufs-weather-model wiki if you are unsure how to do this.
This PR has been tested using a branch which is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR
An Issue describing the work contained in this PR has been created either in the subcomponent(s) or in the ufs-weather-model. The Issue should be created in the repository that is most relevant to the changes in contained in the PR. The Issue and the dependent sub-component PR
are specified below.
If new or updated input data is required by this PR, it is clearly stated in the text of the PR.
Instructions: All subsequent sections of text should be filled in as appropriate.
The information provided below allows the code managers to understand the changes relevant to this PR, whether those changes are in the ufs-weather-model repository or in a subcomponent repository. Ufs-weather-model code managers will use the information provided to add any applicable labels, assign reviewers and place it in the Commit Queue. Once the PR is in the Commit Queue, it is the PR owner's responsiblity to keep the PR up-to-date with the develop branch of ufs-weather-model.
Description
Provide a detailed description of what this PR does. What bug does it fix, or what feature does it add? Is a change of answers expected from this PR? Are any library updates included in this PR (modulefiles etc.)?
Notes:
/work/noaa/nems/bliu/RT/NEMSfv3gfs/input-data-20210930/FV3_hafs_input_data
/work/noaa/nems/bliu/RT/NEMSfv3gfs/input-data-20210930/WW3_input_data_20211101
into the corresponding input-data-20210930 dir, e.g.
/work/noaa/nems/emc.nemspara/RT/NEMSfv3gfs/input-data-20210930/
Issue(s) addressed
Testing
How were these changes tested? What compilers / HPCs was it tested with? Are the changes covered by regression tests? (If not, why? Do new tests need to be added?) Have regression tests and unit tests (utests) been run? On which platforms and with which compilers? (Note that unit tests can only be run on tier-1 platforms)
Regression tests, including both existing and new ones, went through successfully on Orion.
Dependencies