-
Notifications
You must be signed in to change notification settings - Fork 388
Adds option to directly force tidal boundary #284
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
Adds option to directly force tidal boundary #284
Conversation
Testing
|
|
@mark-petersen, note I only implemented this for RK4 because at present because of #217, although we could probably extend this to split explicit without too much trouble. Given that a primary need for this is to support testing of wetting and drying, which is only implemented for RK4 at present, I'm not sure we need to support split explicit to start. |
|
Hm, this is interesting @mark-petersen. When I rebased onto ocean/develop the thickness_source approach improved in quality... Did you update the thickness tendency terms anytime recently? The phase lag is decreased, which is great! |
ea4b726 to
29f40d0
Compare
This ensures that exact tidal boundary can be obtained
29f40d0 to
7fd8c26
Compare
|
@mark-petersen, this also is needed by the drying slope cases too and it works when incorporated. I'm ready for it to be merged pending your checks (using the drying slope prototype as a half-verification). Note the tidal amplitude is forced on the left side and results are as expected too using the |
mark-petersen
left a comment
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.
@pwolfram if you are happy with this, go ahead and merge. I will do full testing and bfb comparisons when I merge coastal into ocean/develop.
Adds option to directly force with tidal boundary This ensures that exact tidal boundary can be obtained via the new 'config_tidal_forcing_type'='direct' option, which is a direct application of the free surface.
|
Thanks @mark-petersen! |
…stal Adds option to directly force with tidal boundary This ensures that exact tidal boundary can be obtained via the new 'config_tidal_forcing_type'='direct' option, which is a direct application of the free surface.
This PR is an accumulation of PRs into the ocean/coastal branch. We are bringing them in at once for efficiency: MPAS-Dev#285, MPAS-Dev#289, MPAS-Dev#284, MPAS-Dev#295, MPAS-Dev#310, MPAS-Dev#311, MPAS-Dev#312, MPAS-Dev#335, MPAS-Dev#354, MPAS-Dev#356, MPAS-Dev#358, MPAS-Dev#359, MPAS-Dev#365, MPAS-Dev#371
…stal Adds option to directly force with tidal boundary This ensures that exact tidal boundary can be obtained via the new 'config_tidal_forcing_type'='direct' option, which is a direct application of the free surface.
This PR is an accumulation of PRs into the ocean/coastal branch. We are bringing them in at once for efficiency: MPAS-Dev#285, MPAS-Dev#289, MPAS-Dev#284, MPAS-Dev#295, MPAS-Dev#310, MPAS-Dev#311, MPAS-Dev#312, MPAS-Dev#335, MPAS-Dev#354, MPAS-Dev#356, MPAS-Dev#358, MPAS-Dev#359, MPAS-Dev#365, MPAS-Dev#371
This PR is an accumulation of PRs into the ocean/coastal branch. We are bringing them in at once for efficiency: MPAS-Dev#285, MPAS-Dev#289, MPAS-Dev#284, MPAS-Dev#295, MPAS-Dev#310, MPAS-Dev#311, MPAS-Dev#312, MPAS-Dev#335, MPAS-Dev#354, MPAS-Dev#356, MPAS-Dev#358, MPAS-Dev#359, MPAS-Dev#365, MPAS-Dev#371





This adds an additional option that allows direct forcing of the tidal boundary, instead
of use of a thickness tendency to apply the tidal boundary.
The test case has been distinguished into these two separate options:
thickness_sourcethat uses restoring to apply the tidal boundary condition via a thickness tendencydirectthat sets the layer thicknesses to obtain a desired sea surface height