[MITgcm-support] How does MITgcm handle the 2D problem

[q li]

I got it. Thank you very much, Jean-Michel.

Li


________________________________
 From: Jean-Michel Campin <jmc at ocean.mit.edu>
To: mitgcm-support at mitgcm.org 
Sent: Friday, December 7, 2012 9:10 PM
Subject: Re: [MITgcm-support] How does MITgcm handle the 2D problem
 
Hi Li,

Yes, no "boundary condition" in the missing direction.
the 1 grid point value is copied over the full over regions (1-Olx:0
and sNx+1:sNx+Olx) so that all gradient along x will vanish.

Cheers,
Jean-Michel

On Fri, Dec 07, 2012 at 01:10:55AM -0800, q li wrote:
> Hi Jean-Michel,
> 
> Thanks for the quick reply.
> 
> Does this imply that no boundary condition  is needed in the missing direction? Or a pseudo-periodic condition?
> 
> Best regards,
> 
> Li
> 
> 
> ________________________________
>  From: Jean-Michel Campin <jmc at ocean.mit.edu>
> To: mitgcm-support at mitgcm.org 
> Sent: Friday, December 7, 2012 1:11 PM
> Subject: Re: [MITgcm-support] How does MITgcm handle the 2D problem
>  
> Hi Li,
> 
> The way a 2-D (x-z or y-z) set-up works is quiet simple, 
> there is just 1 grid point in the missing direction (respectively, y or x),
> still periodic along this direction, therefore all gradients
> are zero; there is no boundary in the missing direction, 
> and the 2 horizontal components of the velocity are stepped forward
> (so that coriolis effects are accounted for).
> 
> Does this answers your question ?
> 
> Cheers,
> Jean-Michel
> 
> On Thu, Dec 06, 2012 at 05:09:34PM -0800, q li wrote:
> > Hi,
> > 
> > I'm confusing about how the MITgcm handles the 2D runs, after receiving a comment from a paper reviewer.
> > 
> > For example, in the "verification/internal_wave" case, tidal forcing is in east-west direction.  delY=5.E3 in the "data" file means only 1 grid in y-direction?
> > On the north/south boundary, how come u and v are set to be zero? Does it mean u and v have to disappear in the whole domain?
> > 
> > Could anyone give me some hints?
> > 
> > Thanks,
> > 
> > Li
> > 
> > "verification/internal_wave/code/obcs_calc.F"
> > 
> > 
> > C         Northern OB, template for forcing
> >       IF (useOrlanskiNorth) THEN
> >         CALL ORLANSKI_NORTH(
> >      &          bi, bj, futureTime,
> >      &          uVel, vVel, wVel, theta, salt,
> >      &          myThid )
> >       ELSE
> >         DO K=1,Nr
> >           DO I=1-Olx,sNx+Olx
> >             OBNv(I,K,bi,bj)=0.
> >             OBNu(I,K,bi,bj)=0.
> >             OBNt(I,K,bi,bj)=tRef(K)
> >             OBNs(I,K,bi,bj)=sRef(K)
> > #ifdef ALLOW_NONHYDROSTATIC
> >             OBNw(I,K,bi,bj)=0.
> > #endif
> >           ENDDO
> >         ENDDO
> >       ENDIF
> 
> > _______________________________________________
> > MITgcm-support mailing list
> > MITgcm-support at mitgcm.org
> > http://mitgcm.org/mailman/listinfo/mitgcm-support
> 
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support

> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support


_______________________________________________
MITgcm-support mailing list
MITgcm-support at mitgcm.org
http://mitgcm.org/mailman/listinfo/mitgcm-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20121207/4f7ff42c/attachment.htm>