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

[Jean-Michel Campin]

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