Ignore:
Timestamp:
2017-02-21T13:53:54+01:00 (4 years ago)
Author:
flavoni
Message:

update NEMO documentation in trunk

File:
1 edited

Legend:

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

    r6997 r7705  
    1818 
    1919\newpage 
    20 $\ $\newline    % force a new ligne 
     20$\ $\newline    % force a new line 
    2121 
    2222Having defined the continuous equations in Chap.~\ref{PE} and chosen a time  
     
    2626directory routines as well as the DOM (DOMain) directory.  
    2727 
    28 $\ $\newline    % force a new lign 
     28$\ $\newline    % force a new line 
    2929 
    3030% ================================================================ 
     
    268268 
    269269The total size of the computational domain is set by the parameters \np{jpiglo},  
    270 \np{jpjglo} and \np{jpkdta} in the $i$, $j$ and $k$ directions respectively. They are  
     270\np{jpjglo} and \np{jpkglo} in the $i$, $j$ and $k$ directions respectively. They are  
    271271given as namelist variables in the \ngn{namcfg} namelist.  
    272  
    273 Note that are other namelist variables in the \ngn{namcfg} namelist that refer to 
    274  the domain size.  
    275 The two variables \np{jpidta} and \np{jpjdta} may be larger than \np{jpiglo}, \np{jpjglo} 
    276 when the user wants to use only a sub-region of a given configuration. This is  
    277 the "zoom" capability described in \S\ref{MISC_zoom}. In most applications of  
    278 the model, $jpidta=jpiglo$, $jpjdta=jpjglo$, and $jpizoom=jpjzoom=1$. Parameters  
    279 $jpi$ and $jpj$ refer to the size of each processor subdomain when the code is  
    280 run in parallel using domain decomposition (\key{mpp\_mpi} defined, see  
    281 \S\ref{LBC_mpp}). 
    282  
    283  
    284 $\ $\newline    % force a new lign 
     272%%% 
     273%%% 
     274%%% 
     275Parameters $jpi$ and $jpj$ refer to the size of each processor subdomain when the code is  
     276run in parallel using domain decomposition (\key{mpp\_mpi} defined, see \S\ref{LBC_mpp}). 
     277 
     278 
     279$\ $\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" 
     283and add list of fields : 
     284case 1: read in domain.nc 
     285case 2: defined in userdef\_hrg\/zgr.F90 
     286longitude, latitude, domaine size  
     287number of points 
     288factor scales (e1, e2, e3) 
     289coriolis 
     290k\_top, k\_bottom (first and last ocean level) 
     291periodicity 
     292} 
     293%%% 
     294 
     295% ================================================================ 
     296% Domain: List of fields needed 
     297% ================================================================ 
     298\section  [Domain: Needed fields] 
     299      {Domain: Needed fields} 
     300\label{DOM_fields} 
     301The ocean mesh ($i.e.$ the position of all the scalar and vector points) is defined  
     302by the transformation that gives $(\lambda,\varphi,z)$ as a function of $(i,j,k)$.  
     303The grid-points are located at integer or integer and a half values of as indicated  
     304in Table~\ref{Tab_cell}. The associated scale factors are defined using the   
     305analytical first derivative of the transformation \eqref{Eq_scale_factors}. These  
     306definitions are done in two modules given by example, \mdl{userdef\_hgr} and \mdl{userdef\_zgr}, which  
     307provide the horizontal and vertical meshes, respectively. Otherwise all needed fields can be read in file \np{cn\_domcfg} specified in \ngn{namcfg}. 
     308  
     309The needed fields for domain are:  
     310 
     311geographic position : 
     312 
     313longitude : glamt , glamu , glamv and glamf  (at T, U, V and F point) 
     314 
     315latitude : gphit , gphiu , gphiv and gphif (at T, U, V and F point) 
     316 
     317Coriolis parameter (if domain not on the sphere):  ff\_f  and  ff\_t (at T and F point) 
     318 
     319Scale 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 { 
     327say something about ie1e2u\_v, e1e2u , e1e2v 
     328 
     329and add list of fields : 
     330case 1: read in domain.nc 
     331case 2: defined in userdef\_hrg\/zgr.F90 
     332longitude, latitude, domaine size 
     333number of points 
     334factor scales (e1, e2, e3) 
     335coriolis 
     336k\_top, k\_bottom (first and last ocean level) 
     337periodicity 
     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 
     356% ------------------------------------------------------------------------------------------------------------- 
     357%        Needed fields  
     358% ------------------------------------------------------------------------------------------------------------- 
     359%\subsection{List of needed fields to build DOMAIN} 
     360%\label{DOM_fields_list} 
     361 
    285362 
    286363% ================================================================ 
     
    436513the output grid written when $\np{nn\_msh} \not=0$ is no more equal to the input grid. 
    437514 
    438 $\ $\newline    % force a new lign 
     515$\ $\newline    % force a new line 
    439516 
    440517% ================================================================ 
Note: See TracChangeset for help on using the changeset viewer.