You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ashjbarnes in one of the demo sessions I recall you said that one of your boundaries cannot fall completely on land.
I don't understand why that is. Is it because of the open boundary conditions? Perhaps if one of the boundary is completely land then we can change to bounded boundary conditions for that boundary?
In any case, if indeed we can't have one of the boundaries fall completely on land then the package should at least spit out a message to the user if they happen to select a region for which this is a problem.
The text was updated successfully, but these errors were encountered:
I think I've had a test run crash when boundaries were entirely on land and assumed that this was why but I might be wrong! I don't think that it would make much sense to do this - MOM6 will be perfectly happy if you just give it no OBC on that side, but then you'd need to configure MOM_input accordingly I guess
Adding a test for this and printing something helpful is a good idea
@ashjbarnes in one of the demo sessions I recall you said that one of your boundaries cannot fall completely on land.
I don't understand why that is. Is it because of the open boundary conditions? Perhaps if one of the boundary is completely land then we can change to bounded boundary conditions for that boundary?
In any case, if indeed we can't have one of the boundaries fall completely on land then the package should at least spit out a message to the user if they happen to select a region for which this is a problem.
The text was updated successfully, but these errors were encountered: