[MITgcm-devel] verification/seaice_obcs

[Jean-Michel Campin]

Hi Dimitris,

Not sure where the problem is.
e.g., using obcs:
uwind(i=Nx) has 2 center neighbours XC(Nx-1) & XC(Nx) which should receive
valid values (and unaffected by the exchanges) from exf
and it should not be a problem to interpolate the wind to this location.
In addition, we are not solving the momentum eq at this location
since it's either at the OBC or further outside the OBC, although 
it's probably needed for KPP(i=Nx-1) and other stuff like that.

and if not using obcs, we can agree that the domain needs to be 
closed at both end when the grid is different at both end: 
e.g., N-S edges, we would add 2 walls at j=1 & j=Ny, 
like we do with Lat-Lon grid when tricky terms
(e.g. some side drag with fancy Horiz. viscosity) are used.

Please give us more details on what is wrong.

Jean-Michel

On Sat, May 10, 2008 at 07:50:41AM -0700, Dimitris Menemenlis wrote:
> Jean-Michel, I am still pondering how best to proceed with the  
> seaice_obcs test.
> 
> One (additional) issue with having open boundaries at edge of domain  
> is that
> the forcing is wrong at the edges. Specifically the XC/XG and YC/YG  
> information
> in the overlap regions is mangled up, which causes exf_interp to  
> generate wrong
> uwind at i=Nx and wrong vwind at j=Ny.
> 
> How should I proceed? Should I move the open boundaries in seaice_obcs  
> a few
> point from the edge? Chris warned me that there might be some issues  
> with
> specifying open boundaries away from the edge and that you were  
> looking into it.
> 
> Please advise, Dimitris
> 
> Dimitris Menemenlis <menemenlis at jpl.nasa.gov>
> Jet Propulsion Lab, California Institute of Technology
> MS 300-323, 4800 Oak Grove Dr, Pasadena CA 91109-8099
> tel: 818-354-1656;  cell: 818-625-6498;  fax: 818-393-6720
> 
> On May 5, 2008, at 4:51 PM, Jean-Michel Campin wrote:
> 
> >An other thing:
> >who is supposed to update the output.txt of seaice_obcs ?
> >Otherwise, (since April 26) if something (wrong) happens to this set- 
> >up,
> >we will not be able to catch it.
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel