Changeset 7669 for branches/2016/dev_merge_2016/DOC/TexFiles/Chapters/Chap_DOM.tex

Timestamp:

2017-02-10T18:16:26+01:00 (7 years ago)

Author:

flavoni

Message:

starting update of tex book for new configurations interface

File:

• branches/2016/dev_merge_2016/DOC/TexFiles/Chapters/Chap_DOM.tex (modified) (4 diffs)

branches/2016/dev_merge_2016/DOC/TexFiles/Chapters/Chap_DOM.tex

@@ -18 +18 @@
 
 \newpage
-$\ $\newline    % force a new ligne
+$\ $\newline    % force a new line
 
 Having defined the continuous equations in Chap.~\ref{PE} and chosen a time 
@@ -26 +26 @@
 directory routines as well as the DOM (DOMain) directory. 
 
-$\ $\newline    % force a new lign
+$\ $\newline    % force a new line
 
 % ================================================================
@@ -268 +268 @@
 
 The total size of the computational domain is set by the parameters \np{jpiglo}, 
-\np{jpjglo} and \np{jpkdta} in the $i$, $j$ and $k$ directions respectively. They are 
+\np{jpjglo} and \np{jpkglo} in the $i$, $j$ and $k$ directions respectively. They are 
 given as namelist variables in the \ngn{namcfg} namelist. 
-
-Note that are other namelist variables in the \ngn{namcfg} namelist that refer to
- the domain size. 
-The two variables \np{jpidta} and \np{jpjdta} may be larger than \np{jpiglo}, \np{jpjglo}
-when the user wants to use only a sub-region of a given configuration. This is 
-the "zoom" capability described in \S\ref{MISC_zoom}. In most applications of 
-the model, $jpidta=jpiglo$, $jpjdta=jpjglo$, and $jpizoom=jpjzoom=1$. Parameters 
-$jpi$ and $jpj$ refer to the size of each processor subdomain when the code is 
-run in parallel using domain decomposition (\key{mpp\_mpi} defined, see 
-\S\ref{LBC_mpp}).
-
-
-$\ $\newline    % force a new lign
+%%%
+%%%
+%%%
+Parameters $jpi$ and $jpj$ refer to the size of each processor subdomain when the code is 
+run in parallel using domain decomposition (\key{mpp\_mpi} defined, see \S\ref{LBC_mpp}).
+
+
+$\ $\newline    % force a new line
+
+%%%
+\sfcomment {Hereafter I want to create new subsection 4.2: "fields needed by opa engine or something like this"
+and add list of fields :
+case 1: read in domain.nc
+case 2: defined in userdef\_hrg\/zgr.F90
+longitude, latitude, domaine size 
+number of points
+factor scales (e1, e2, e3)
+coriolis
+k\_top, k\_bottom (first and last ocean level)
+periodicity
+}
+%%%
+
+% ================================================================
+% Domain: List of fields needed
+% ================================================================
+\section  [Domain: Needed fields]
+      {Domain: Needed fields}
+\label{DOM_fields}
+The ocean mesh ($i.e.$ the position of all the scalar and vector points) is defined 
+by the transformation that gives $(\lambda,\varphi,z)$ as a function of $(i,j,k)$. 
+The grid-points are located at integer or integer and a half values of as indicated 
+in Table~\ref{Tab_cell}. The associated scale factors are defined using the  
+analytical first derivative of the transformation \eqref{Eq_scale_factors}. These 
+definitions are done in two modules given by example, \mdl{userdef\_hgr} and \mdl{userdef\_zgr}, which 
+provide the horizontal and vertical meshes, respectively. Otherwise all needed fields can be read in file \np{cn\_domcfg} specified in \ngn{namcfg}.
+ 
+The needed fields for domain are: 
+
+geographic position :
+
+longitude : glamt , glamu , glamv and glamf  (at T, U, V and F point)
+
+latitude : gphit , gphiu , gphiv and gphif (at T, U, V and F point)
+
+Coriolis parameter (if domain not on the sphere):  ff\_f  and  ff\_t (at T and F point)
+
+Scale factors : e1t, e1u, e1v and e1f (on i direction),
+
+   e2t, e2u, e2v and e2f (on j direction)
+
+   and ie1e2u\_v, e1e2u , e1e2v   
+
+%%%
+\sfcomment {
+say something about ie1e2u\_v, e1e2u , e1e2v
+
+and add list of fields :
+case 1: read in domain.nc
+case 2: defined in userdef\_hrg\/zgr.F90
+longitude, latitude, domaine size
+number of points
+factor scales (e1, e2, e3)
+coriolis
+k\_top, k\_bottom (first and last ocean level)
+periodicity
+----
+        int ORCA ;
+   int ORCA\_index ;
+   int jpiglo ; j, k
+   int jperio ;
+   int ln_zco ; zps, sco
+   int ln_isfcav ;
+   double glamt(t, y, x) ; u,v,f
+   double gphit(t, y, x) ; u,v,f
+   double e1t(t, y, x) ; u,v,w,
+   double e2t(t, y, x) ; u,v,w
+   double ff\_f(t, y, x) ;  double ff\_t(t, y, x) ;
+   double e3t\_1d(t, z) ;
+   double e3w\_1d(t, z) ;
+   double e3t\_0(t, z, y, x) ; u0, v0 , w0
+----
+}
+
+% -------------------------------------------------------------------------------------------------------------
+%        Needed fields 
+% -------------------------------------------------------------------------------------------------------------
+%\subsection{List of needed fields to build DOMAIN}
+%\label{DOM_fields_list}
+
 
 % ================================================================
@@ -436 +513 @@
 the output grid written when $\np{nn\_msh} \not=0$ is no more equal to the input grid.
 
-$\ $\newline    % force a new lign
+$\ $\newline    % force a new line
 
 % ================================================================