-
Notifications
You must be signed in to change notification settings - Fork 58
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
Bring in feature/hafs.v2.0.1 back to develop #299
Conversation
07/03/2024 (From @BijuThomas-NAA and @BinLiu-NOAA)
…tbl_new after the latest HAFS submodule syncing.
ush/hafs_filter_topo.sh, and ush/hafs_make_orog.sh. These updates are needed with the latest hafs_utils.fd sync. Also, the filter_topo and make_orog_gsl steps are substantialy speeded up through OMP threading.
…r.fd Update scripts/exhafs_enkf_hx.sh
gsi module on WCOSS2.
HAFS.v2.0.1, due to issues associated with the new updated restart file (sfc_data) with the latest UFS_UTILS chgres_cube updates. This is a temporary solution. The longer term solution is to update hafs_datool, VI, and GSI/DA so that they can work with the update restart files. * Update parm/mom6/regional/hafs_mom6.input.IN needed for MOM6 update. * Update scripts/exhafs_analysis.sh to link a new crtm fix file.
…cale-aware Tiedtke for HAFS
…dvars.conf, hafs.conf to improve the SLP and short range forecast. In convert_axi_xy.f90, the threshold for shallow composite vortex is changed from p_obs.lt.91510 (HAFS vortex SLP) to vslp.lt.92010 (TCVitals SLP)
@lisa-bengtsson's change to improve convection/radiation interaction.
Add parm/mom6/regional_hafs.v2.0.1a and parm/mom6/regional_hafs.v2.0.1b.
update parm/forecast/globnest/input*.nml.tmp according to its regional counterpart.
…ability enabled. * Update parm/ww3/regional/ww3_grid_?.inp by adding &OUTS USSP =1, IUSSP = 3, STK_WN = 0.04, 0.110, 0.3305 / * Update parm/mom6/regional_hafs.v2.0.1a/hafs_mom6.input.IN with USE_WAVES = True
also set the moving nest d02 increments along the domain boundaries (within 10 grid points) as zeros. (From @XuLu-NOAA and @BinLiu-NOAA)
…s from Hyun-Sook Kim (AOML).
Update parm/hafs.v2.0.1a.conf with lim_fac=2.7
- Updating run.ver for hafs and RTOFS versions. - Update scripts/exhafs_obs_prep.sh, which properly handles tempdrop obs processing errors/warnings.
@JunghoonShin-NOAA, @nriveratorres-NOAA, @LinZhu-NOAA, @ChuankaiWang-NOAA, could you please help to cover the regression tests for this PR on the following platforms, respectively? Thanks! |
Regression tests on WCOSS2 have already passed successfully without issues. |
Using batch instead of windfall to avoid queueing. |
Regression tests passed successfully on Orion |
All regression tests completed successfully on Jet. But the ocean input data for the test case (2020 Laura 13L) does not exist on Jet anymore, and so I used Hurricane Lee as a test case. |
Since Lin is on travel, I conducted the RT on Hera. All regression tests were completed successfully on Hera |
@ZhanZhang-NOAA or @KathrynNewman We need another approval from the repo owners before merging this PR. Appreciated it if you get a chance to review and approve from your end. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving changes bringing feature/hafs.v2.0.1 to develop. RTs passed on all platforms.
Description of changes
Bring in the HAFSv2.0.1 development and configurations used by 2024 HFIP real-time parallel experiments back to HAFS develop branch. More details/configurations for 2024 HFIP HAFSv2.0.1A and B real-time parallel experiments can be found below.
Issues addressed (optional)
If this PR addresses one or more issues, please provide link(s) to the issue(s) here.
Contributors (optional)
If others worked on this PR besides the author, please include their user names here (using @Mention if possible).
EMC hurricane project team with lots of collaborators from the UFS Hurricane Application Team.
Tests conducted
What testing has been conducted on the PR thus far? Describe the nature of any scientific or technical tests, including relevant details about the configuration(s) (e.g., cold versus warm start, number of cycles, forecast length, whether data assimilation was performed, etc). What platform(s) were used for testing?
Technical, retrospective, and real-time parallel testing were conducted.
Application-level regression test status
Running the HAFS application-level regression tests is currently performed by code reviewers after the developer creates the initial PR. As regression tests are conducted, the testers should use the checklist below to indicate successful regression tests. You may add other tests as needed. If a test fails, do not check the box. Instead, describe the failure in the PR comments, noting the platform where the test failed.