-
Notifications
You must be signed in to change notification settings - Fork 245
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
OBC registry #476
OBC registry #476
Conversation
- Can use Flather on outflow end, which behaves much better than prior choice.
- Kelvin wave and tidal bay so far.
- Put back supercritical_initialize_topography as well, just in case we want to try for the shock with the land masking.
Also got shelfwave to compile.
- Oops. Rotated is too strong now?
- The BT_OBC structure still has them (probably needs some exchanges??). - Need to obsolete READ_OBC_ETA, READ_OBC_UV, and READ_OBC_TS. They aren't being used in any of our tests (speaking of coverage). - No answer change.
By the way, this changes answers for CCS. It does so because Matt's code loads up the segment variables while the old barotropic code was using OBC%ubt_outer instead. |
OK, this looks right. I'll handle the PR today. Looking at the correlation of OBC and update_OBC_CSp in arguments makes it seem that there is redundancy but as you point out, there is a circular dependency in the types themselves. Idea for the future (i.e. not needed now), we could rename things if we think of MOM_boundary_update.F90 as an "OBC driver" and the current MOM_open_boundary.F90 as the "segment provider". |
There might be a way to have OBC inside the update_OBC_CSp instead. Perhaps
rename it first. I agree about saving it for later though.
…On Tue, Apr 25, 2017 at 4:53 AM, Alistair Adcroft ***@***.***> wrote:
OK, this looks right. I'll handle the PR today.
Looking at the correlation of OBC and update_OBC_CSp in arguments makes it
seem that there is redundancy but as you point out, there is a circular
dependency in the types themselves. Idea for the future (i.e. not needed
now), we could rename things if we think of MOM_boundary_update.F90 as an
"OBC driver" and the current MOM_open_boundary.F90 as the "segment
provider".
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<NOAA-GFDL#476 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAbIHi6QnU2Ks5xGNfhK9-_qpoaInl3_ks5rzezegaJpZM4NFhaJ>
.
|
Exactly, and agreed.
…--
Dr Alistair Adcroft (Alistair.Adcroft@noaa.gov)
Princeton University Tel: (609) 987-5073
NOAA/GFDL, 201 Forrestal Road, Princeton, NJ 08540
On Tue, Apr 25, 2017 at 1:19 PM, Kate Hedstrom <notifications@github.com>
wrote:
There might be a way to have OBC inside the update_OBC_CSp instead. Perhaps
rename it first. I agree about saving it for later though.
On Tue, Apr 25, 2017 at 4:53 AM, Alistair Adcroft <
***@***.***>
wrote:
> OK, this looks right. I'll handle the PR today.
>
> Looking at the correlation of OBC and update_OBC_CSp in arguments makes
it
> seem that there is redundancy but as you point out, there is a circular
> dependency in the types themselves. Idea for the future (i.e. not needed
> now), we could rename things if we think of MOM_boundary_update.F90 as an
> "OBC driver" and the current MOM_open_boundary.F90 as the "segment
> provider".
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <NOAA-GFDL#476 (comment)>, or
mute
> the thread
> <https://github.com/notifications/unsubscribe-
auth/AAbIHi6QnU2Ks5xGNfhK9-_qpoaInl3_ks5rzezegaJpZM4NFhaJ>
> .
>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<NOAA-GFDL#476 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFlo8w_aa8DSnVa44zGNwOFhHY07J4p_ks5rzis4gaJpZM4NFhaJ>
.
|
- This option is defaulted to False to retain previous answers, but should be set to True for new experiments in order to make the Flather OBC routine consistent with the barotropic solver - This option only applies for regional OBC cases with Tides and scalar self-attraction and loading + Try at fixing issue mom-ocean#476 - Will change answers for problems with OBCs. - Get Matt's patch to compile again Co-authored-by: Kate Hedstrom <kshedstrom@alaska.edu>
- This option is defaulted to False to retain previous answers, but should be set to True for new experiments in order to make the Flather OBC routine consistent with the barotropic solver - This option only applies for regional OBC cases with Tides and scalar self-attraction and loading + Try at fixing issue mom-ocean#476 - Will change answers for problems with OBCs. - Get Matt's patch to compile again Co-authored-by: Kate Hedstrom <kshedstrom@alaska.edu>
Several things: