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 9019 for branches/2017/dev_merge_2017/DOC/TexFiles/Chapters/Chap_DOM.tex – NEMO

Ignore:
Timestamp:
2017-12-13T15:58:53+01:00 (6 years ago)
Author:
timgraham
Message:

Merge of dev_CNRS_2017 into branch

File:
1 edited

Legend:

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

    r7705 r9019  
    268268 
    269269The total size of the computational domain is set by the parameters \np{jpiglo},  
    270 \np{jpjglo} and \np{jpkglo} in the $i$, $j$ and $k$ directions respectively. They are  
    271 given as namelist variables in the \ngn{namcfg} namelist.  
     270\np{jpjglo} and \np{jpkglo} in the $i$, $j$ and $k$ directions respectively.  
    272271%%% 
    273272%%% 
     
    278277 
    279278$\ $\newline    % force a new line 
    280  
    281 %%% 
    282 \sfcomment {Hereafter I want to create new subsection 4.2: "fields needed by opa engine or something like this" 
    283 and add list of fields : 
    284 case 1: read in domain.nc 
    285 case 2: defined in userdef\_hrg\/zgr.F90 
    286 longitude, latitude, domaine size  
    287 number of points 
    288 factor scales (e1, e2, e3) 
    289 coriolis 
    290 k\_top, k\_bottom (first and last ocean level) 
    291 periodicity 
    292 } 
    293 %%% 
    294279 
    295280% ================================================================ 
     
    303288The grid-points are located at integer or integer and a half values of as indicated  
    304289in Table~\ref{Tab_cell}. The associated scale factors are defined using the   
    305 analytical first derivative of the transformation \eqref{Eq_scale_factors}. These  
    306 definitions are done in two modules given by example, \mdl{userdef\_hgr} and \mdl{userdef\_zgr}, which  
    307 provide the horizontal and vertical meshes, respectively. Otherwise all needed fields can be read in file \np{cn\_domcfg} specified in \ngn{namcfg}. 
     290analytical first derivative of the transformation \eqref{Eq_scale_factors}.  
     291Necessary fields for configuration definition are: \\ 
     292Geographic position : 
     293 
     294longitude : glamt , glamu , glamv and glamf  (at T, U, V and F point) 
     295 
     296latitude : gphit , gphiu , gphiv and gphif (at T, U, V and F point)\\ 
     297Coriolis parameter (if domain not on the sphere):  
     298 
     299 ff\_f  and  ff\_t (at T and F point)\\ 
     300Scale factors :  
    308301  
    309 The needed fields for domain are:  
    310  
    311 geographic position : 
    312  
    313 longitude : glamt , glamu , glamv and glamf  (at T, U, V and F point) 
    314  
    315 latitude : gphit , gphiu , gphiv and gphif (at T, U, V and F point) 
    316  
    317 Coriolis parameter (if domain not on the sphere):  ff\_f  and  ff\_t (at T and F point) 
    318  
    319 Scale factors : e1t, e1u, e1v and e1f (on i direction), 
    320  
    321    e2t, e2u, e2v and e2f (on j direction) 
    322  
    323    and ie1e2u\_v, e1e2u , e1e2v    
    324  
    325 %%% 
    326 \sfcomment { 
    327 say something about ie1e2u\_v, e1e2u , e1e2v 
    328  
    329 and add list of fields : 
    330 case 1: read in domain.nc 
    331 case 2: defined in userdef\_hrg\/zgr.F90 
    332 longitude, latitude, domaine size 
    333 number of points 
    334 factor scales (e1, e2, e3) 
    335 coriolis 
    336 k\_top, k\_bottom (first and last ocean level) 
    337 periodicity 
    338 ---- 
    339         int ORCA ; 
    340    int ORCA\_index ; 
    341    int jpiglo ; j, k 
    342    int jperio ; 
    343    int ln_zco ; zps, sco 
    344    int ln_isfcav ; 
    345    double glamt(t, y, x) ; u,v,f 
    346    double gphit(t, y, x) ; u,v,f 
    347    double e1t(t, y, x) ; u,v,w, 
    348    double e2t(t, y, x) ; u,v,w 
    349    double ff\_f(t, y, x) ;  double ff\_t(t, y, x) ; 
    350    double e3t\_1d(t, z) ; 
    351    double e3w\_1d(t, z) ; 
    352    double e3t\_0(t, z, y, x) ; u0, v0 , w0 
    353 ---- 
    354 } 
    355  
     302 e1t, e1u, e1v and e1f (on i direction), 
     303 
     304 e2t, e2u, e2v and e2f (on j direction) 
     305 
     306 and ie1e2u\_v, e1e2u , e1e2v    
     307  
     308e1e2u , e1e2v are u and v surfaces (if gridsize reduction in some straits)\\ 
     309ie1e2u\_v is a flag to flag set u and  v surfaces are neither read nor computed.\\ 
     310  
     311These fields can be read in an domain input file which name is setted in \np{cn\_domcfg} parameter specified in \ngn{namcfg}. 
     312\namdisplay{namcfg} 
     313or they can be defined in an analytical way in MY\_SRC directory of the configuration. 
     314For Reference Configurations of NEMO input domain files are supplied by NEMO System Team. For analytical definition of input fields two routines are supplied: \mdl{userdef\_hgr} and \mdl{userdef\_zgr}. They are an example of GYRE configuration parameters, and they are available in NEMO/OPA\_SRC/USR directory, they provide the horizontal and vertical mesh.  
    356315% ------------------------------------------------------------------------------------------------------------- 
    357316%        Needed fields  
     
    446405\label{DOM_hgr_msh_choice} 
    447406 
    448 The user has three options available in defining a horizontal grid, which involve  
    449 the namelist variable \np{jphgr\_mesh} of the \ngn{namcfg} namelist.  
    450 \begin{description} 
    451 \item[\np{jphgr\_mesh}=0]  The most general curvilinear orthogonal grids. 
    452 The coordinates and their first derivatives with respect to $i$ and $j$ are provided 
    453 in a input file (\ifile{coordinates}), read in \rou{hgr\_read} subroutine of the domhgr module. 
    454 \item[\np{jphgr\_mesh}=1 to 5] A few simple analytical grids are provided (see below).  
    455 For other analytical grids, the \mdl{domhgr} module must be modified by the user.  
    456 \end{description} 
    457  
    458 There are two simple cases of geographical grids on the sphere. With  
    459 \np{jphgr\_mesh}=1, the grid (expressed in degrees) is regular in space,  
    460 with grid sizes specified by parameters \np{ppe1\_deg} and \np{ppe2\_deg},  
    461 respectively. Such a geographical grid can be very anisotropic at high latitudes  
    462 because of the convergence of meridians (the zonal scale factors $e_1$  
    463 become much smaller than the meridional scale factors $e_2$). The Mercator  
    464 grid (\np{jphgr\_mesh}=4) avoids this anisotropy by refining the meridional scale  
    465 factors in the same way as the zonal ones. In this case, meridional scale factors  
    466 and latitudes are calculated analytically using the formulae appropriate for  
    467 a Mercator projection, based on \np{ppe1\_deg} which is a reference grid spacing  
    468 at the equator (this applies even when the geographical equator is situated outside  
    469 the model domain).  
    470 %%% 
    471 \gmcomment{ give here the analytical expression of the Mercator mesh} 
    472 %%% 
    473 In these two cases (\np{jphgr\_mesh}=1 or 4), the grid position is defined by the  
    474 longitude and latitude of the south-westernmost point (\np{ppglamt0}  
    475 and \np{ppgphi0}). Note that for the Mercator grid the user need only provide  
    476 an approximate starting latitude: the real latitude will be recalculated analytically,  
    477 in order to ensure that the equator corresponds to line passing through $t$-  
    478 and $u$-points.   
    479  
    480 Rectangular grids ignoring the spherical geometry are defined with  
    481 \np{jphgr\_mesh} = 2, 3, 5. The domain is either an $f$-plane (\np{jphgr\_mesh} = 2,  
    482 Coriolis factor is constant) or a beta-plane (\np{jphgr\_mesh} = 3, the Coriolis factor  
    483 is linear in the $j$-direction). The grid size is uniform in meter in each direction,  
    484 and given by the parameters \np{ppe1\_m} and \np{ppe2\_m} respectively.  
    485 The zonal grid coordinate (\textit{glam} arrays) is in kilometers, starting at zero  
    486 with the first $t$-point. The meridional coordinate (gphi. arrays) is in kilometers,  
    487 and the second $t$-point corresponds to coordinate $gphit=0$. The input  
    488 variable \np{ppglam0} is ignored. \np{ppgphi0} is used to set the reference  
    489 latitude for computation of the Coriolis parameter. In the case of the beta plane,  
    490 \np{ppgphi0} corresponds to the center of the domain. Finally, the special case  
    491 \np{jphgr\_mesh}=5 corresponds to a beta plane in a rotated domain for the  
    492 GYRE configuration, representing a classical mid-latitude double gyre system.  
    493 The rotation allows us to maximize the jet length relative to the gyre areas  
    494 (and the number of grid points).  
    495  
    496 The choice of the grid must be consistent with the boundary conditions specified  
    497 by \np{jperio}, a parameter found in \ngn{namcfg} namelist (see {\S\ref{LBC}). 
    498407 
    499408% ------------------------------------------------------------------------------------------------------------- 
     
    684593(Fig.~\ref{Fig_zgr}). 
    685594 
    686 If the ice shelf cavities are opened (\np{ln\_isfcav}=~true~}), the definition of $z_0$ is the same.  
     595If the ice shelf cavities are opened (\np{ln\_isfcav}=~true~), the definition of $z_0$ is the same.  
    687596However, definition of $e_3^0$ at $t$- and $w$-points is respectively changed to: 
    688597\begin{equation} \label{DOM_zgr_ana} 
     
    737646\begin{table}     \begin{center} \begin{tabular}{c||r|r|r|r} 
    738647\hline 
    739 \textbf{LEVEL}& \textbf{gdept}& \textbf{gdepw}& \textbf{e3t }& \textbf{e3w  } \\ \hline 
     648\textbf{LEVEL}& \textbf{gdept\_1d}& \textbf{gdepw\_1d}& \textbf{e3t\_1d }& \textbf{e3w\_1d  } \\ \hline 
    7406491  &  \textbf{  5.00}   &       0.00 & \textbf{ 10.00} &  10.00 \\   \hline 
    7416502  &  \textbf{15.00} &    10.00 &   \textbf{ 10.00} &  10.00 \\   \hline 
Note: See TracChangeset for help on using the changeset viewer.