HAFSv0.3 moving-nesting related coupling, vortex initialization, and data assimilation capabilities #132
Conversation
…e' into feature/hafs_moving_nest
…lobal moving nest tests from Bill Ramstrom. Only for the prescribed nest moving currently.
…31' into feature/multi_nests (Bill and Bin).
… feature/multi_nests
*Update submodule sorc/hafs_utils.fd *Configure two C96 globnest configurations: -hafs_globnest2_C96_static.conf: two same level static nests -hafs_globnest2tele_C96_static.conf: two telescopic static nests
hafs_globnest2tele_C96_static.conf (two telescopic nests) have run throught the forecast jobs.
… feature/multi_nests
… feature/multi_nests
…sv0p2a_phase2_AL.conf.
… into feature/multi_nests
… into feature/multi_nests
…ature/multi_nests
…ature/multi_nests
…final' into feature/multi_nests
|
Regression tests passed on Hera after some minor modifications. @BinLiu-NOAA @evankalina The post process numbers need to be increased (e.g., changing from 2 nodes to 4 nodes) to pass the tests on Hera for HAFS_rt_regional_atm_only, HAFS_rt_regional_static_atm_ocn, HAFS_rt_regional_atm_ocn_wav, HAFS_rt_regional_mvnest_vida, HAFS_rt_regional_static_atm_wav |
Thanks, @panll! I am updating the ATM_POST_RESOURCES to use 4 nodes with 20 PEs per node as follows: 4:ppn=20:tpp=1TOTAL_TASKS80NCTSK20OMP_THREADS107:59:00">Hopefully this will work fine. |
Regression tests passed on WCOSS(Cray) after using classic NetCDF option(-n4) for the mppnccombine executable. |
*Turn off delivering hafs.trak.atcfunix.orig file to NOSCRUB dir.
BinLiu-NOAA
force-pushed
the
feature/hafsv0.3_phase2
branch
from
3f961da
to
832ba6b
Compare
|
Hello Bin, |
…n ufs-weather-model. *Fix the forecast job/task hanging/failure on wcoss_dell_p3.
@LinZhu-NOAA, I have just pushed a fix for the forecast job hanging/failure on wcoss_dell_p3. Please "git pull" the latest changes and rewind the failed tasks. And they should now go through successfully. The issue was the inconsistent modules loaded in modulefile.hafs.wcoss_dell_p3. Thanks! |
|
@BinLiu-NOAA The regression tests completed successfully on WCOSS-Dell after updating the modules. |
setting ll_bin size and max_points. *Use the weighting function of exp(-r/r_scale) for the empirical linear interpolation method, currently r_scale is hardcoded as 2 km, which can be improved in the future so that it can be automatically determined/adjusted. *These fixes/changes are based on discussions among Bin, Yonghui, and Zhan.
…sh so that it is consitent with the value currently hardcoded in the source code.
|
Thanks to @panll, @mrinalbiswas, @LinZhu-NOAA, @JunghoonShin-NOAA, @BijuThomas-NOAA for conducing the application level regression tests! And we have also fixed the hafsvi_pre-/postproc interpolation issues. So, I think this PR is ready merge now. Also, @evankalina, since this PR contains lots of developments and commits, I was thinking of merging this PR by keeping its commit log. Does is sound good to you? Thanks! |
BinLiu-NOAA
added
the
Ready to Merge
…rt/HAFS branches.
hafs_sfc_climo_gen.x in atm_prep.
|
@BinLiu-NOAA Keeping the list of commits sounds good to me. Congratulations on getting this PR ready! |
|
Thanks All! Merging to close this PR now. |
Description of changes
The HAFSv0.3 phase2 configuration contains the latest HAFS moving nesting, coupling, vortex initialization, data assimilation capabilities, and it points to the latest develop branch (as of 04/12/2022) of ufs-weather-model. Besides, the hafs_utils.fd and hafs_gsi.fd were also synced with their corresponding develop/master branches recently.
Issues addressed (optional)
If this PR addresses one or more issues, please provide link(s) to the issue(s) here.
Tests conducted
This feature/hafsv0.3_phase2 branch has been tested on various HAFS supported platforms.
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.