-
Notifications
You must be signed in to change notification settings - Fork 259
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
Regional inlinepost #364
Regional inlinepost #364
Conversation
@junwang-noaa Would you please update postxconfig-NT-fv3lam.txt with the latest UPP develop branch? The UPP side had the update for renaming FV3/LAM dataset names as PRSLEV and NATLEV. Thanks! |
@BinLiu-NOAA @BenjaminBlake-NOAA @JamesAbeles-NOAA @WenMeng-NOAA To run regional inline post on hera, please do the following:
A sample run directory is on hera at: If you want to run current regional inline post test, after 1), please do ii) run ./rt.sh So far I did limited tests with regional_latlon, roated_latlon and Lamber_conformal grids. Please let me know if you have any questions. Thanks |
@junwang-noaa Could you add a new itag for regional in-line post which process 47 isobaric levels instead 57? You may find the itag used by off-line post at /scratch1/NCEPDEV/stmp2/Wen.Meng/post_fv3_2018101500 on hera. |
@WenMeng-NOAA, I want to confirm the itag under your directory is used by
regional in-line post only, is that correct? In the current setting ,the
same itag (57 isobaric levels) is used for both global and regional inline
post, but we can change it to use a different itag for regional inline post.
…On Thu, Jan 28, 2021 at 3:47 PM WenMeng-NOAA ***@***.***> wrote:
@junwang-noaa <https://github.com/junwang-noaa> Could you add a new itag
for regional in-line post which process 47 isobaric levels instead 57? You
may find the itag used by off-line post at
/scratch1/NCEPDEV/stmp2/Wen.Meng/post_fv3_2018101500 on hera.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#364 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TP7MRQSTMXLZVYP3RTS4HEMXANCNFSM4V7YDZQQ>
.
|
@junwang-noaa That's right. The 57 levels is for GFS only due to the model output 127 layers. The regional application still use 47(64 model layers). I would like to have @BenjaminBlake-NOAA or @ericaligo-NOAA to confirm from their parallel configuration. |
The regional LAM has npz = 60 or 60 model layers.
…On 1/28/2021 4:13 PM, WenMeng-NOAA wrote:
@junwang-noaa <https://github.com/junwang-noaa> That's right. The 57
levels is for GFS only due to the model output 127 layers. The
regional application still use 47(64 model layers). I would like to
have @BenjaminBlake-NOAA <https://github.com/BenjaminBlake-NOAA> or
@ericaligo-NOAA <https://github.com/ericaligo-NOAA> to confirm from
their parallel configuration.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#364 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALQ75MKUYZOW3RNVNYEPLFDS4HHOTANCNFSM4V7YDZQQ>.
|
Yes, we do have 60 model layers, this is about the isobaric levels in lam
post.
On Thu, Jan 28, 2021 at 5:40 PM ericaligo-NOAA <[email protected]>
wrote:
… The regional LAM has npz = 60 or 60 model layers.
On 1/28/2021 4:13 PM, WenMeng-NOAA wrote:
>
> @junwang-noaa <https://github.com/junwang-noaa> That's right. The 57
> levels is for GFS only due to the model output 127 layers. The
> regional application still use 47(64 model layers). I would like to
> have @BenjaminBlake-NOAA <https://github.com/BenjaminBlake-NOAA> or
> @ericaligo-NOAA <https://github.com/ericaligo-NOAA> to confirm from
> their parallel configuration.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#364 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ALQ75MKUYZOW3RNVNYEPLFDS4HHOTANCNFSM4V7YDZQQ
>.
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#364 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TOG6IHE4HHQHGQLDRTS4HRXFANCNFSM4V7YDZQQ>
.
|
@junwang-noaa @WenMeng-NOAA This is what we are using for itag in the regional post, and it looks like we do use 47 isobaric levels. &NAMPGB |
That's what I see as well.
…On 1/29/2021 8:59 AM, BenjaminBlake-NOAA wrote:
@junwang-noaa <https://github.com/junwang-noaa> @WenMeng-NOAA
<https://github.com/WenMeng-NOAA> This is what we are using for itag
in the regional post, and it looks like we do use 47 isobaric levels.
&NAMPGB
KPO=47,PO=1000.,975.,950.,925.,900.,875.,850.,825.,800.,775.,750.,725.,700.,675.,650.,625.,600.,575.,550.,525.,500.,475.,450.,425.,400.,375.,350.,325.,300.,275.,250.,225.,200.,175.,150.,125.,100.,70.,50.,30.,20.,10.,7.,5.,3.,2.,1.,
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#364 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALQ75MIUGMNE7NSELARWDP3S4K5K3ANCNFSM4V7YDZQQ>.
|
@BenjaminBlake-NOAA Thanks for confirming that. I update the code to use47
isobaric levels.
…On Fri, Jan 29, 2021 at 8:59 AM BenjaminBlake-NOAA ***@***.***> wrote:
@junwang-noaa <https://github.com/junwang-noaa> @WenMeng-NOAA
<https://github.com/WenMeng-NOAA> This is what we are using for itag in
the regional post, and it looks like we do use 47 isobaric levels.
&NAMPGB
KPO=47,PO=1000.,975.,950.,925.,900.,875.,850.,825.,800.,775.,750.,725.,700.,675.,650.,625.,600.,575.,550.,525.,500.,475.,450.,425.,400.,375.,350.,325.,300.,275.,250.,225.,200.,175.,150.,125.,100.,70.,50.,30.,20.,10.,7.,5.,3.,2.,1.,
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#364 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TMYOZ2BG34BEDC3GD3S4K5K3ANCNFSM4V7YDZQQ>
.
|
Note that for the grib2 files on the native levels, 64 are indicated
even though we're currently running with 60:
<shortname>HGT_ON_HYBRID_LVL</shortname>
<pname>HGT</pname>
<level>1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16.
17. 18. 19. 20. 21. 22. 23. 24.
25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42.
43. 44. 45. 46. 47. 48.
49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64.</level>
…On 1/29/2021 9:06 AM, Jun Wang wrote:
@BenjaminBlake-NOAA Thanks for confirming that. I update the code to use47
isobaric levels.
On Fri, Jan 29, 2021 at 8:59 AM BenjaminBlake-NOAA
***@***.***>
wrote:
> @junwang-noaa <https://github.com/junwang-noaa> @WenMeng-NOAA
> <https://github.com/WenMeng-NOAA> This is what we are using for itag in
> the regional post, and it looks like we do use 47 isobaric levels.
>
> &NAMPGB
>
>
KPO=47,PO=1000.,975.,950.,925.,900.,875.,850.,825.,800.,775.,750.,725.,700.,675.,650.,625.,600.,575.,550.,525.,500.,475.,450.,425.,400.,375.,350.,325.,300.,275.,250.,225.,200.,175.,150.,125.,100.,70.,50.,30.,20.,10.,7.,5.,3.,2.,1.,
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
>
<#364 (comment)>,
> or unsubscribe
>
<https://github.com/notifications/unsubscribe-auth/AI7D6TMYOZ2BG34BEDC3GD3S4K5K3ANCNFSM4V7YDZQQ>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#364 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALQ75MMTHZOJFIAB7KPXFMDS4K6FVANCNFSM4V7YDZQQ>.
|
412f7c6
@BrianCurtis-NOAA May I ask how orion RT is doing? |
[!1018]bcurtis@Orion-login-2:/work/noaa/nems/emc.nemspara/autort/tests/auto$ squeue --user=bcurtis |
* upstream/develop: Updatetemplate; Fix model slowness when using threading; Update WW3 for porting and threading issues (ufs-community#383) update MOM6 to GFDL 20210308 main branch commit (ufs-community#458) Regional inlinepost (ufs-community#364) correct benchmark diag_tables for coupled model configurations; move bm_ic directory out of inputdata directory; use aws ec2 for CI test; auto-rt fixes (ufs-community#426)
Description
1)Code changes have been added for inline post capability for regional applications (HAFS and LAM). The supported output grids are "regional_latlon" for HAFS, "rotated_latlon" and "lambert_comformal" for LAM.
2) remove quilting restriction when generating forecast grid, which is used by esmf field creation for both coupled runs and quilting.
3) rt script is updated. The regional tests using same ICs will use the ICs in fv3_regional_control/INPUT, rather than using same set of INPUT data in each regional_test/INPUT.
4) add suite_FV3_GFS_v15_thompson_mynn.xml suite for LAM 3km parallel run
5) add timing information for each RT tests
Due to the upp update, the global inline post test results will change. Inline post results will be added to fv3_ccpp_regional_quilt and baseline results will be added to new test fv3_ccpp_regional_quilt_hafs. There is no result change for all other tests.
Issue(s) addressed
Link the issues to be closed with this PR, whether in this repository, or in another repository.
Testing
Testing has been done on hera,orion and dell with regional regression etst regional_quilt and regional_quilt_hafs tests and high resolution LAM and HAFS tests. The results have been verified against standalone post results.
RT is done on:
Note: Orion is really slow, the RT tests still stay in the job queue since this morning. I will make the merge after CI test is done, will have attach the log file when it is done.
Dependencies
Related PR: