[MITgcm-support] [EXTERNAL] topography with OBCS

[Dimitris Menemenlis]

Hi Andreas, I had assumed that your initial tests were an attempt to reproduce a small region from a larger-domain simulation.  If you don’t extract the U/V/T/S OBCS fields from the correct locations in the larger-domain simulation, you might end up with a mask mismatch issue.  But based on your discussion with Martin, this seems not to be the case.

If your simulations are easy to repeat, you could you try turning off
 useOBCSsponge    = .FALSE.,
 useOBCSbalance   = .FALSE.,
and then turning these back on one at a time in order to isolate the bug.
I don’t think that the bug lives in useOBCSprescribe for 3D variables.

Dimitris

> On Jun 21, 2020, at 2:57 AM, Andreas Klocker <andreas.klocker at utas.edu.au> wrote:
> 
> Dimitris,
> What do you mean by extracting my boundary conditions at the correct location?
> cheers,
> Andreas
> 
> From: MITgcm-support <mitgcm-support-bounces at mitgcm.org> on behalf of Dimitris Menemenlis <dmenemenlis at gmail.com>
> Sent: Friday, 19 June 2020 1:12 PM
> To: MITgcm Support <mitgcm-support at mitgcm.org>
> Subject: Re: [MITgcm-support] [EXTERNAL] topography with OBCS
>  
> Hi Andreas, are you sure that you are extracting your boundary conditions at the correct location?
> You could be off by one grid cell, which could cause this problem.  Dimitris
> 
> 
>> On Jun 18, 2020, at 6:21 PM, Andreas Klocker <andreas.klocker at utas.edu.au> wrote:
>> 
>> Hi,
>> 
>> I am trying to set up a regional model configuration with OBCS. For some reason the model seems to introduce salinities where I actually have bathymetry (see attached figure; bathymetry left, salinities right). Salinities this low definitely do not exist in the files containing the bounday conditions. Is it necessary to set the open boundary exactly to where I have ocean, or should the bathymetry file take care of this by telling the model there should be nothing happening in case of zero water depth?
>> 
>> Here's my data.obcs file:
>> 
>> # Open-boundaries
>>  &OBCS_PARM01
>> 
>>  OB_Iwest  = 600*1,
>>  OB_Ieast  = 600*-1,
>>  OB_Jsouth = 2600*1,
>>  OB_Jnorth = 2600*-1,
>> 
>>  useOBCSsponge    = .TRUE.,
>>  useOBCSbalance   = .TRUE.,
>>  useOBCSprescribe = .TRUE.,
>> 
>>  useOrlanskiWest  = .FALSE.,
>>  useOrlanskiEast  = .FALSE.,
>>  useOrlanskiSouth = .FALSE.,
>>  useOrlanskiNorth = .FALSE.,
>> 
>>  OBWuFile = 'OWU',
>>  OBWvFile = 'OWV',
>>  OBWtFile = 'OWT',
>>  OBWsFile = 'OWS',
>> 
>>  OBEuFile = 'OEU',
>>  OBEvFile = 'OEV',
>>  OBEtFile = 'OET',
>>  OBEsFile = 'OES',
>> 
>>  OBSuFile = 'OSU',
>>  OBSvFile = 'OSV',
>>  OBStFile = 'OST',
>>  OBSsFile = 'OSS',
>> 
>>  OBNuFile = 'ONU',
>>  OBNvFile = 'ONV',
>>  OBNtFile = 'ONT',
>>  OBNsFile = 'ONS',
>> 
>> # OBCS_monitorFreq= 86400.,
>> # OBCS_monSelect = 1,
>>  &
>> 
>> # Orlanski parameters
>>  &OBCS_PARM02
>> # Cmax=0.45,
>> # cVelTimeScale=1000.,
>>  &
>> 
>>  &OBCS_PARM03
>>  Urelaxobcsinner=864000.,
>>  Urelaxobcsbound=86400.,
>>  Vrelaxobcsinner=864000.,
>>  Vrelaxobcsbound=86400.,
>>  spongeThickness=40.,
>>  &
>> 
>> Thanks in advance!
>> Andreas
>> 
>> 
>> University of Tasmania Electronic Communications Policy (December, 2014). 
>> This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.
>> <obcs.png>_______________________________________________
>> MITgcm-support mailing list
>> MITgcm-support at mitgcm.org
>> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support