-
Notifications
You must be signed in to change notification settings - Fork 188
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
grid
not identical to model.grid
#1501
Comments
I think we should change the defaults as suggested by #1245 so this is uncommon. |
Good idea. Following the discussion, and the fact that people seem to be using high order advection schemes like |
Changing the default would make inflating halos less common. I still think it would be useful to print a warning/info when halos are inflated so the user knows |
I'm happy to put a warning if people agree. What would we say exactly and where would we say it? |
How about this? @warn "Inflating model grid halo size to ($Hx, $Hy, $Hz) and recreating grid. " *
"The model grid will be different from the input grid. To avoid this warning, " *
"pass halo=($Hx, $Hy, $Hz) when constructing the grid." |
Sounds great! I have added it in my branch. I will close this issue and we cna modify this when the branch makes its way as a PR. Soon I hope! |
@ali-ramadhan and I discovered today in developing
fjp/flat-for-shallow-water-model
thatgrid
is set up with default halos butmodel.grid
actually has the correct halos needed for the advection scheme. Note that the advection scheme is not specified until after the grid is created so given the current framework I think this is necessary. I realize this might be less than ideal but as long as you are focusing on the physcial domain, the two agree exactly.Is this a concern?
The text was updated successfully, but these errors were encountered: