if and why mpp_get_boundary should be called when .not. bounded_domain #1020
Replies: 2 comments 2 replies
-
Hello @TingLei-NOAA! Shawn Cebula - EPIC End User Support |
Beta Was this translation helpful? Give feedback.
2 replies
-
@RatkoVasic-NOAA Sure. The Jeid 's D-A wind conversions issue had been fixed by D. Holdaway with the help from R. Benson. I think this question could be closed. Thanks |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear UFS developers,
Would you tell me if and why the mpp_get_boundary should only be called when bounded_domain is not true (namely, global runs)?
From the codes itself, seems this should work for regional runs (bounded_domain=.true.). But, it was found there would be problems when it was used in jedi 's D-A wind conversion for fv3-lam (regional fv3). And in UFS dyn_core.F90, there is
if( it==n_split .and. gridstruct%grid_type<4 .and. .not. gridstruct%bounded_domain) then ! Prevent accumulation of rounding errors at overlapped domain edges: call mpp_get_boundary(u, v, domain, ebuffery=ebuffer, & nbufferx=nbuffer, gridtype=DGRID_NE )
So, any clarification and explanation are appreciated.
Beta Was this translation helpful? Give feedback.
All reactions