New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
Changeset 3989 for branches/2013/dev_r3853_CNRS9_ConfSetting/DOC/TexFiles/Chapters/Chap_LBC.tex – NEMO

Ignore:
Timestamp:
2013-07-24T11:48:35+02:00 (11 years ago)
Author:
clevy
Message:

Configuration setting/Step3 and doc, see ticket:#1074

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/2013/dev_r3853_CNRS9_ConfSetting/DOC/TexFiles/Chapters/Chap_LBC.tex

    r3294 r3989  
    11% ================================================================ 
    2 % Chapter Ñ Lateral Boundary Condition (LBC)  
     2% Chapter Lateral Boundary Condition (LBC)  
    33% ================================================================ 
    44\chapter{Lateral Boundary Condition (LBC) } 
     
    2525%OPA allows land and topography grid points in the computational domain due to the presence of continents or islands, and includes the use of a full or partial step representation of bottom topography. The computation is performed over the whole domain, i.e. we do not try to restrict the computation to ocean-only points. This choice has two motivations. Firstly, working on ocean only grid points overloads the code and harms the code readability. Secondly, and more importantly, it drastically reduces the vector portion of the computation, leading to a dramatic increase of CPU time requirement on vector computers.  The current section describes how the masking affects the computation of the various terms of the equations with respect to the boundary condition at solid walls. The process of defining which areas are to be masked is described in \S\ref{DOM_msk}. 
    2626 
     27Options are defined through the \ngn{namlbc} namelist variables. 
    2728The discrete representation of a domain with complex boundaries (coastlines and  
    2829bottom topography) leads to arrays that include large portions where a computation  
     
    148149% Boundary Condition around the Model Domain 
    149150% ================================================================ 
    150 \section{Model Domain Boundary Condition (\jp{jperio})} 
     151\section{Model Domain Boundary Condition (\np{jperio})} 
    151152\label{LBC_jperio} 
    152153 
     
    156157 
    157158% ------------------------------------------------------------------------------------------------------------- 
    158 %        Closed, cyclic, south symmetric (\jp{jperio} = 0, 1 or 2)  
     159%        Closed, cyclic, south symmetric (\np{jperio} = 0, 1 or 2)  
    159160% ------------------------------------------------------------------------------------------------------------- 
    160 \subsection{Closed, cyclic, south symmetric (\jp{jperio} = 0, 1 or 2)} 
     161\subsection{Closed, cyclic, south symmetric (\np{jperio} = 0, 1 or 2)} 
    161162\label{LBC_jperio012} 
    162163 
    163164The choice of closed, cyclic or symmetric model domain boundary condition is made  
    164 by setting \jp{jperio} to 0, 1 or 2 in file \mdl{par\_oce}. Each time such a boundary  
     165by setting \np{jperio} to 0, 1 or 2 in namelist \ngn{namcfg}. Each time such a boundary  
    165166condition is needed, it is set by a call to routine \mdl{lbclnk}. The computation of  
    166167momentum and tracer trends proceeds from $i=2$ to $i=jpi-1$ and from $j=2$ to  
     
    295296 domain and the overlapping rows. The number of rows to exchange (known as  
    296297 the halo) is usually set to one (\jp{jpreci}=1, in \mdl{par\_oce}). The whole domain  
    297  dimensions are named \jp{jpiglo}, \jp{jpjglo} and \jp{jpk}. The relationship between  
     298 dimensions are named \np{jpiglo}, \np{jpjglo} and \jp{jpk}. The relationship between  
    298299 the whole domain and a sub-domain is: 
    299300\begin{eqnarray}  
     
    419420\end{itemize} 
    420421 
     422Options are defined through the \ngn{namobc} namelist variables. 
    421423The package resides in the OBC directory. It is described here in four parts: the  
    422424boundary geometry (parameters to be set in \mdl{obc\_par}), the forcing data at  
     
    455457Logical flag  &                 &                            &                     \\ 
    456458\hline 
    457 West          & \jp{jpiwob} $>= 2$         &  \jp{jpjwd}$>= 2$          &  \jp{jpjwf}<= \jp{jpjglo}-1 \\ 
     459West          & \jp{jpiwob} $>= 2$         &  \jp{jpjwd}$>= 2$          &  \jp{jpjwf}<= \np{jpjglo}-1 \\ 
    458460lp\_obc\_west & $i$-index of a $u$ point   & $j$ of a $T$ point   &$j$ of a $T$ point \\ 
    459461\hline 
    460 East            & \jp{jpieob}$<=$\jp{jpiglo}-2&\jp{jpjed} $>= 2$         & \jp{jpjef}$<=$ \jp{jpjglo}-1 \\ 
     462East            & \jp{jpieob}$<=$\np{jpiglo}-2&\jp{jpjed} $>= 2$         & \jp{jpjef}$<=$ \np{jpjglo}-1 \\ 
    461463 lp\_obc\_east  & $i$-index of a $u$ point    & $j$ of a $T$ point & $j$ of a $T$ point \\ 
    462464\hline 
    463 South           & \jp{jpjsob} $>= 2$         & \jp{jpisd} $>= 2$          & \jp{jpisf}$<=$\jp{jpiglo}-1 \\ 
     465South           & \jp{jpjsob} $>= 2$         & \jp{jpisd} $>= 2$          & \jp{jpisf}$<=$\np{jpiglo}-1 \\ 
    464466lp\_obc\_south  & $j$-index of a $v$ point   & $i$ of a $T$ point   & $i$ of a $T$ point \\ 
    465467\hline 
    466 North           & \jp{jpjnob} $<=$ \jp{jpjglo}-2& \jp{jpind} $>= 2$        & \jp{jpinf}$<=$\jp{jpiglo}-1 \\ 
     468North           & \jp{jpjnob} $<=$ \np{jpjglo}-2& \jp{jpind} $>= 2$        & \jp{jpinf}$<=$\np{jpiglo}-1 \\ 
    467469lp\_obc\_north  & $j$-index of a $v$ point      & $i$  of a $T$ point & $i$ of a $T$ point \\ 
    468470\hline 
     
    754756%----------------------------------------------------------------------------------------------- 
    755757 
     758Options are defined through the \ngn{nambdy} \ngn{nambdy\_index}  
     759\ngn{nambdy\_dta} \ngn{nambdy\_dta2} namelist variables. 
    756760The BDY module is an alternative implementation of open boundary 
    757761conditions for regional configurations. It implements the Flow 
     
    10241028%----------------------------------------------------------------------------------------------- 
    10251029 
    1026 To be written.... 
    1027  
    1028  
    1029  
    1030  
     1030Options are defined through the  \ngn{nambdy\_tide} namelist variables. 
     1031 To be written.... 
     1032 
     1033 
     1034 
     1035 
Note: See TracChangeset for help on using the changeset viewer.