Changeset 1843


Ignore:
Timestamp:
2010-04-15T10:47:52+02:00 (11 years ago)
Author:
gm
Message:

DEV_r1826_DOC : use the input file index command, see ticket: #658

Location:
branches/DEV_r1826_DOC/DOC/TexFiles/Chapters
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • branches/DEV_r1826_DOC/DOC/TexFiles/Chapters/Chap_DOM.tex

    r1831 r1843  
    1414%  - daymod: definition of the time domain (nit000, nitend andd the calendar) 
    1515%  -geo2ocean:  how to switch from geographic to mesh coordinate 
    16 - domclo:  closed sea and lakes.... management of closea sea area : specific to global configuration, both forced and coupled 
     16   - domclo:  closed sea and lakes.... management of closea sea area : specific to global configuration, both forced and coupled 
    1717 
    1818\gmcomment{STEVEN :maybe a picture of the directory structure in the introduction  
     
    392392\begin{description} 
    393393\item[\jp{jphgr\_mesh}=0]  The most general curvilinear orthogonal grids. 
    394 The coordinates and their first derivatives with respect to $i$ and $j$ are  
    395 provided in a file, read in \rou{hgr\_read} subroutine of the domhgr module. 
     394The coordinates and their first derivatives with respect to $i$ and $j$ are provided 
     395in a input file (\ifile{coordinates}), read in \rou{hgr\_read} subroutine of the domhgr module. 
    396396\item[\jp{jphgr\_mesh}=1 to 5] A few simple analytical grids are provided (see below).  
    397397For other analytical grids, the \mdl{domhgr} module must be modified by the user.  
     
    442442%        Grid files 
    443443% ------------------------------------------------------------------------------------------------------------- 
    444 \subsection{Grid files} 
     444\subsection{Output Grid files} 
    445445\label{DOM_hgr_files} 
    446446 
     
    507507Contrary to the horizontal grid, the vertical grid is computed in the code and no  
    508508provision is made for reading it from a file. The only input file is the bathymetry  
    509 (in meters)\footnote{N.B. in full step $z$-coordinate, a \textit{bathy\_level} file can  
    510 replace the \textit{bathy\_meter} file, so that the computation of the number of  
    511 wet ocean point in each water column is by-passed}. After reading the bathymetry,  
    512 the algorithm for vertical grid definition differs between the different options: 
     509(in meters) (\ifile{bathy\_meter})  
     510\footnote{N.B. in full step $z$-coordinate, a \ifile{bathy\_level} file can replace the  
     511\ifile{bathy\_meter} file, so that the computation of the number of wet ocean point  
     512in each water column is by-passed}.  
     513After reading the bathymetry, the algorithm for vertical grid definition differs  
     514between the different options: 
    513515\begin{description} 
    514516\item[\textit{zco}] set a reference coordinate transformation $z_0 (k)$, and set $z(i,j,k,t)=z_0 (k)$. 
     
    553555domain width at the central latitude. This is meant for the "EEL-R5" configuration,  
    554556a periodic or open boundary channel with a seamount.  
    555 \item[\np{ntopo} = 1] read a bathymetry. The bathymetry file (Netcdf format)  
     557\item[\np{ntopo} = 1] read a bathymetry. The \ifile{bathy\_meter} file (Netcdf format)  
    556558provides the ocean depth (positive, in meters) at each grid point of the model grid.  
    557559The bathymetry is usually built by interpolating a standard bathymetry product  
     
    560562(all levels are masked). 
    561563\end{description} 
    562  
    563 When using the rigid lid approximation (\key{dynspg\_rl} is defined) isolated land  
    564 masses (islands) must be identified by negative integers in the input bathymetry file  
    565 (see \S\ref{MISC_solisl}). 
    566564 
    567565When a global ocean is coupled to an atmospheric model it is better to represent  
     
    802800gives the number of ocean levels ($i.e.$ those that are not masked) at each  
    803801$t$-point. mbathy is computed from the meter bathymetry using the definiton of  
    804 gdept as the number of $t$-points which gdept $\leq$ bathy. Note that in version  
    805 NEMO v2.3, the user still has to provide the "level" bathymetry in a NetCDF 
    806 file when using the full step option (\np{ln\_zco}), rather than the bathymetry  
    807 in meters: both will be allowed in future versions. 
     802gdept as the number of $t$-points which gdept $\leq$ bathy.  
    808803 
    809804Modifications of the model bathymetry are performed in the \textit{bat\_ctl}  
    810805routine (see \mdl{domzgr} module) after mbathy is computed. Isolated grid points  
    811806that do not communicate with another ocean point at the same level are eliminated. 
    812  
    813 In the case of the rigid-lid approximation when islands occur in the computational  
    814 domain (\np{ln\_dynspg\_rl}=.true. and \key{island} is defined), the \textit{mbathy}  
    815 array must be provided and takes values from $-N$ to \jp{jpk}-1. It provides the  
    816 following information: $mbathy(i,j) = -n, \ n \in \left] 0,N \right]$, $t$-points are  
    817 land points on the $n^{th}$ island ; $mbathy(i,j) =0$, $t$-points are land points  
    818 on the main land (continent) ; $mbathy(i,j) =k$, the first $k$ $t$- and $w$-points  
    819 are ocean points, the others are points below the ocean floor.  
    820  
    821 This is used to compute the island barotropic stream function used in the rigid lid  
    822 computation (see \S\ref{MISC_solisl}). 
    823807 
    824808From the \textit{mbathy} array, the mask fields are defined as follows: 
  • branches/DEV_r1826_DOC/DOC/TexFiles/Chapters/Chap_TRA.tex

    r1831 r1843  
    848848\np{ngeo\_flux\_const}, which is also a namelist parameter. If it is set to 2,  
    849849a spatially varying geothermal heat flux is introduced which is provided  
    850 in the geothermal\_heating.nc NetCDF file (Fig.\ref{Fig_geothermal}). 
     850in the \ifile{geothermal\_heating} NetCDF file (Fig.\ref{Fig_geothermal}). 
    851851 
    852852% ================================================================ 
Note: See TracChangeset for help on using the changeset viewer.