-
Notifications
You must be signed in to change notification settings - Fork 232
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixes needed to "not" extend OBCs beyond domain.
- Added %Flather logical to segment type to differentiate Flather (for barotropic) from Orlanski (baroclinic) boundary conditions. - Bugfix: Barotropic-direction south had wrong sign for setting the tangential ubt. Does not appear to change answers? - Changed syntax of OBC_SEGMENT_%%% string to allow multiple boundary conditions type per segment, e.g. FLATHER,ORLANSKI - zonal_mass_flux() and meridional_mass_flux() in continuity_PPM now use %Flather instead of %radiation just before reconciling fluxes with the barotropic fluxes. - Fixed need to extend boundaries beyond domain in run-time parameters. Extended domains used to be needed to avoid masking the corner vorticity points. Added code to detect corner joins of segments and handle explicitly. - Removed code to interpret I=-1:N+1 (extend boundaries no longer needed). - Use "hack" in setup_*_point_obc() to extend segments by one point (in code) to recover "corner" behavior of old OBCs. - Added back setting of tangential velocity components in continuity_PPM. - set_Flather_data() has commented out code to set "h" across corners when segments are not extended. - Cleaned up setting of "direction" in setup_u_point_obc() and setup_v_point_obc(). - Simplied using of directions/flags in continuity_PPM. - No answer changes with consistent switch to SEGMENT parameters. TODO: - Allow coexistence of specified and radiative BCs within zonal_mass_flux() and meridional_mass_flux(). - Understand why the above bugfix did not change answers? - Figure out why extending segments to recover corner behavior is necessary: LAPLACIAN=BIHARMONIC=False still failed, suggesting PV term needs examination.
- Loading branch information
Showing
4 changed files
with
283 additions
and
217 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.