-
Notifications
You must be signed in to change notification settings - Fork 55
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
Data override updates and bugfixes #67
Conversation
call mpp_global_field(Atm%Domain, Atm%lon_bnd, glon_bnd, position=CORNER) | ||
call mpp_global_field(Atm%Domain, Atm%lat_bnd, glat_bnd, position=CORNER) | ||
|
||
if (.NOT.Atm%bounded_domain) call data_override_init (Atm_domain_in = Atm%domain) |
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.
Do we know what the logic behind excluding bounded_domain is here? I know Lauren opened an issue a while ago relating to some unsupported regional model behavior in data override, but that could be unrelated. I would assume there wouldn't be a data_table if the bounded_domain existed because it would never get called in this scenario, but I don't know that for sure.
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.
@GFDL-Eric - this is a topic I'll be bringing up for FMS dev as a whole and data_override in particular. I'll try to make it a topic for the next group meeting.
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.
I will approve when FMS #933 is merged
Removes grid code and variables from SHiELD/coupler_main and fixes data_override_init
Removes outdated logic in simple/coupler_main for data_override_init parsing
Relies upon FMS PR #933