From e8fc2b8636eb35e90d49d0374d9b6fcee19daefa Mon Sep 17 00:00:00 2001
From: Andrew Coward <acc@noc.ac.uk>
Date: Mon, 14 Feb 2022 21:56:20 +0000
Subject: [PATCH] Tidying in chap_DYN.tex and chap_DOM.tex

---
 doc/latex/NEMO/subfiles/chap_DOM.tex | 22 +++++++++++-----------
 doc/latex/NEMO/subfiles/chap_DYN.tex |  6 +++---
 2 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/doc/latex/NEMO/subfiles/chap_DOM.tex b/doc/latex/NEMO/subfiles/chap_DOM.tex
index 4683e57a8..18e850ea4 100644
--- a/doc/latex/NEMO/subfiles/chap_DOM.tex
+++ b/doc/latex/NEMO/subfiles/chap_DOM.tex
@@ -392,16 +392,16 @@ The explicit specification of a range of mesh-related fields are required for
 the definition of a configuration.
 These include:
 
-\begin{clines}
+\begin{forlines}
 integer   Ni0glo, NjOglo, jpkglo       /* global domain sizes (without MPI halos)                */
-logical   l\_Iperio, l\_Jperio         /* lateral global domain b.c.: i- j-periodicity           */
-logical   l\_NFold                     /* lateral global domain b.c.: North Pole folding         */
-char(1)   c\_NFtype                    /*    type of North pole Folding: T or F point            */
+logical   l_Iperio, l_Jperio           /* lateral global domain b.c.: i- j-periodicity           */
+logical   l_NFold                      /* lateral global domain b.c.: North Pole folding         */
+char(1)   c_NFtype                     /*    type of North pole Folding: T or F point            */
 real      glamt, glamu, glamv, glamf   /* geographic longitude (t,u,v and f points respectively) */
 real      gphit, gphiu, gphiv, gphif   /* geographic latitude                                    */
 real      e1t, e1u, e1v, e1f           /* horizontal scale factors                               */
 real      e2t, e2u, e2v, e2f           /* horizontal scale factors                               */
-\end{clines}
+\end{forlines}
 
 The values of the geographic longitude and latitude arrays at indices $i,j$ correspond to
 the analytical expressions of the longitude $\lambda$ and latitude $\varphi$ as a function of $(i,j)$,
@@ -413,12 +413,12 @@ evaluated for the same arguments as $\lambda$ and $\varphi$.
 %% =================================================================================================
 \subsubsection{Optional fields}
 
-\begin{clines}
+\begin{forlines}
                         /* Optional:                                                 */
 int    ORCA, ORCA_index /* configuration name, configuration resolution              */
 double e1e2u, e1e2v     /* U and V surfaces (if grid size reduction in some straits) */
 double ff_f, ff_t       /* Coriolis parameter (if not on the sphere)                 */
-\end{clines}
+\end{forlines}
 
 \NEMO\ can support the local reduction of key strait widths by
 altering individual values of e2u or e1v at the appropriate locations.
@@ -560,7 +560,7 @@ The explicit specification of a range of fields related to the vertical grid are
 the definition of a configuration.
 These include:
 
-\begin{clines}
+\begin{forlines}
 int    ln_zco, ln_zps, ln_sco            /* flags for z-coord, z-coord with partial steps and s-coord    */
 int    ln_isfcav                         /* flag  for ice shelf cavities                                 */
 double e3t_1d, e3w_1d                    /* reference vertical scale factors at T and W points           */
@@ -569,7 +569,7 @@ double e3uw_0, e3vw_0                    /* vertical scale factors 3D coordinate
 int    bottom_level, top_level           /* last wet T-points, 1st wet T-points (for ice shelf cavities) */
                                          /* For reference:                                               */
 float  bathy_metry                       /* bathymetry used in setting top and bottom levels             */
-\end{clines}
+\end{forlines}
 
 This set of vertical metrics is sufficient to describe the initial depth and thickness of
 every gridcell in the model regardless of the choice of vertical coordinate.
@@ -639,11 +639,11 @@ it should be noted here that a successful use of these options requires
 appropriate mask fields to be present in the domain configuration file.
 Among the possibilities are:
 
-\begin{clines}
+\begin{forlines}
 int closea_mask     /* non-zero values in closed sea areas for optional masking                */
 int closea_mask_rnf /* non-zero values in closed sea areas with runoff locations (precip only) */
 int closea_mask_emp /* non-zero values in closed sea areas with runoff locations (total emp)   */
-\end{clines}
+\end{forlines}
 
 %% =================================================================================================
 \subsection{Output grid files}
diff --git a/doc/latex/NEMO/subfiles/chap_DYN.tex b/doc/latex/NEMO/subfiles/chap_DYN.tex
index d827a6c59..4d82795d3 100644
--- a/doc/latex/NEMO/subfiles/chap_DYN.tex
+++ b/doc/latex/NEMO/subfiles/chap_DYN.tex
@@ -916,9 +916,9 @@ As far as tracer conservation is concerned,
 barotropic velocities used to advect tracers must also be updated at \textit{now} time step.
 This implies to change the traditional order of computations in \NEMO:
 most of momentum trends (including the barotropic mode calculation) updated first, tracers' after.
-This \textit{de facto} makes semi-implicit hydrostatic pressure gradient
-(see section \autoref{subsec:DYN_hpg_imp})
-and time splitting not compatible.
+%%This \textit{de facto} makes semi-implicit hydrostatic pressure gradient
+%%(see section \autoref{subsec:DYN_hpg_imp})
+%%and time splitting not compatible.
 Advective barotropic velocities are obtained by using a secondary set of filtering weights,
 uniquely defined from the filter coefficients used for the time averaging (\citet{shchepetkin.mcwilliams_OM05}).
 Consistency between the time averaged continuity equation and the time stepping of tracers is here the key to
-- 
GitLab