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 6140 for trunk/DOC/TexFiles/Chapters/Chap_DOM.tex – NEMO

Ignore:
Timestamp:
2015-12-21T12:35:23+01:00 (8 years ago)
Author:
timgraham
Message:

Merge of branches/2015/dev_merge_2015 back into trunk. Merge excludes NEMOGCM/TOOLS/OBSTOOLS/ for now due to issues with the change of file type. Will sort these manually with further commits.

Branch merged as follows:
In the working copy of branch ran:
svn merge svn+ssh://forge.ipsl.jussieu.fr/ipsl/forge/projets/nemo/svn/trunk@HEAD
Small conflicts due to bug fixes applied to trunk since the dev_merge_2015 was copied. Bug fixes were applied to the branch as well so these were easy to resolve.
Branch committed at this stage

In working copy run:
svn switch svn+ssh://forge.ipsl.jussieu.fr/ipsl/forge/projets/nemo/svn/trunk
to switch working copy

Run:
svn merge --reintegrate svn+ssh://forge.ipsl.jussieu.fr/ipsl/forge/projets/nemo/svn/branches/2015/dev_merge_2015
to merge the branch into the trunk and then commit - no conflicts at this stage.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/DOC/TexFiles/Chapters/Chap_DOM.tex

    r5120 r6140  
    11% ================================================================ 
    2 % Chapter 2 Space and Time Domain (DOM) 
     2% Chapter 2 ——— Space and Time Domain (DOM) 
    33% ================================================================ 
    44\chapter{Space Domain (DOM) } 
     
    364364For both grids here,  the same $w$-point depth has been chosen but in (a) the  
    365365$t$-points are set half way between $w$-points while in (b) they are defined from  
    366 an analytical function: $z(k)=5\,(i-1/2)^3 - 45\,(i-1/2)^2 + 140\,(i-1/2) - 150$.  
     366an analytical function: $z(k)=5\,(k-1/2)^3 - 45\,(k-1/2)^2 + 140\,(k-1/2) - 150$.  
    367367Note the resulting difference between the value of the grid-size $\Delta_k$ and  
    368368those of the scale factor $e_k$. } 
     
    475475(d) hybrid $s-z$ coordinate,  
    476476(e) hybrid $s-z$ coordinate with partial step, and  
    477 (f) same as (e) but with variable volume associated with the non-linear free surface.  
    478 Note that the variable volume option (\key{vvl}) can be used with any of the  
     477(f) same as (e) but in the non-linear free surface (\np{ln\_linssh}=false).  
     478Note that the non-linear free surface can be used with any of the  
    4794795 coordinates (a) to (e).} 
    480480\end{center}   \end{figure} 
    481481%>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
    482482 
    483 The choice of a vertical coordinate, even if it is made through a namelist parameter,  
     483The choice of a vertical coordinate, even if it is made through \ngn{namzgr} namelist parameters,  
    484484must be done once of all at the beginning of an experiment. It is not intended as an  
    485485option which can be enabled or disabled in the middle of an experiment. Three main  
     
    488488(\np{ln\_zps}~=~true), or generalized, $s$-coordinate (\np{ln\_sco}~=~true).  
    489489Hybridation of the three main coordinates are available: $s-z$ or $s-zps$ coordinate  
    490 (Fig.~\ref{Fig_z_zps_s_sps}d and \ref{Fig_z_zps_s_sps}e). When using the variable  
    491 volume option \key{vvl} ($i.e.$ non-linear free surface), the coordinate follow the  
    492 time-variation of the free surface so that the transformation is time dependent:  
    493 $z(i,j,k,t)$ (Fig.~\ref{Fig_z_zps_s_sps}f). This option can be used with full step  
    494 bathymetry or $s$-coordinate (hybrid and partial step coordinates have not  
    495 yet been tested in NEMO v2.3). If using $z$-coordinate with partial step bathymetry 
    496 (\np{ln\_zps}~=~true), ocean cavity beneath ice shelves can be open (\np{ln\_isfcav}~=~true). 
     490(Fig.~\ref{Fig_z_zps_s_sps}d and \ref{Fig_z_zps_s_sps}e). By default a non-linear free surface is used: 
     491the coordinate follow the time-variation of the free surface so that the transformation is time dependent:  
     492$z(i,j,k,t)$ (Fig.~\ref{Fig_z_zps_s_sps}f). When a linear free surface is assumed (\np{ln\_linssh}=true),  
     493the vertical coordinate are fixed in time, but the seawater can move up and down across the z=0 surface  
     494(in other words, the top of the ocean in not a rigid-lid).  
     495The last choice in terms of vertical coordinate concerns the presence (or not) in the model domain  
     496of ocean cavities beneath ice shelves. Setting \np{ln\_isfcav} to true allows to manage ocean cavities,  
     497otherwise they are filled in. 
    497498 
    498499Contrary to the horizontal grid, the vertical grid is computed in the code and no  
    499500provision is made for reading it from a file. The only input file is the bathymetry  
    500 (in meters) (\ifile{bathy\_meter})  
     501(in meters) (\ifile{bathy\_meter}).  
    501502\footnote{N.B. in full step $z$-coordinate, a \ifile{bathy\_level} file can replace the  
    502503\ifile{bathy\_meter} file, so that the computation of the number of wet ocean point  
    503504in each water column is by-passed}.  
     505If \np{ln\_isfcav}~=~true, an extra file input file describing the ice shelf draft  
     506(in meters) (\ifile{isf\_draft\_meter}) is needed and all the location where the isf cavity thinnest 
     507 than \np{rn\_isfhmin} meters are grounded (ie masked).  
     508 
    504509After reading the bathymetry, the algorithm for vertical grid definition differs  
    505510between the different options: 
     
    519524%%% 
    520525 
    521 The arrays describing the grid point depths and vertical scale factors  
    522 are three dimensional arrays $(i,j,k)$ even in the case of $z$-coordinate with  
    523 full step bottom topography. In non-linear free surface (\key{vvl}), their knowledge 
    524 is required at \textit{before}, \textit{now} and \textit{after} time step, while they  
    525 do not vary in time in linear free surface case.  
    526 To improve the code readability while providing this flexibility, the vertical coordinate  
    527 and scale factors are defined as functions of  
    528 $(i,j,k)$ with "fs" as prefix (examples: \textit{fse3t\_b, fse3t\_n, fse3t\_a,}  
    529 for the  \textit{before}, \textit{now} and \textit{after} scale factors at $t$-point)  
    530 that can be either three different arrays when \key{vvl} is defined, or a single fixed arrays.  
    531 These functions are defined in the file \hf{domzgr\_substitute} of the DOM directory.  
    532 They are used throughout the code, and replaced by the corresponding arrays at  
    533 the time of pre-processing (CPP capability). 
     526Unless a linear free surface is used (\np{ln\_linssh}=false), the arrays describing  
     527the grid point depths and vertical scale factors are three set of three dimensional arrays $(i,j,k)$  
     528defined at \textit{before}, \textit{now} and \textit{after} time step. The time at which they are 
     529defined is indicated by a suffix:$\_b$, $\_n$, or $\_a$, respectively. They are updated at each model time step 
     530using a fixed reference coordinate system which computer names have a $\_0$ suffix.  
     531When the linear free surface option is used (\np{ln\_linssh}=true), \textit{before}, \textit{now}  
     532and \textit{after} arrays are simply set one for all to their reference counterpart.  
     533 
    534534 
    535535% ------------------------------------------------------------------------------------------------------------- 
     
    840840%        z*- or s*-coordinate 
    841841% ------------------------------------------------------------------------------------------------------------- 
    842 \subsection{$z^*$- or $s^*$-coordinate (add \key{vvl}) } 
    843 \label{DOM_zgr_vvl} 
     842\subsection{$z^*$- or $s^*$-coordinate (\np{ln\_linssh}=false) } 
     843\label{DOM_zgr_star} 
    844844 
    845845This option is described in the Report by Levier \textit{et al.} (2007), available on  
Note: See TracChangeset for help on using the changeset viewer.