Changeset 11537 for NEMO/trunk/doc/latex/NEMO/subfiles/chap_DIA.tex

Timestamp:

2019-09-12T10:24:48+02:00 (5 years ago)

Author:

clem

Message:

make sure SI3 doc can be compiled, plus small edits

File:

• NEMO/trunk/doc/latex/NEMO/subfiles/chap_DIA.tex (modified) (9 diffs)

NEMO/trunk/doc/latex/NEMO/subfiles/chap_DIA.tex

@@ -125 +125 @@
 
 XIOS may be used to read single file restart produced by \NEMO. Currently only the variables written to
-file \forcode{numror} can be handled by XIOS. To activate restart reading using XIOS, set \np{ln\_xios\_read}\forcode{ = .true. }
+file \forcode{numror} can be handled by XIOS. To activate restart reading using XIOS, set \np{ln\_xios\_read}\forcode{=.true. }
 in \textit{namelist\_cfg}. This setting will be ignored when multiple restart files are present, and default \NEMO
 functionality will be used for reading. There is no need to change iodef.xml file to use XIOS to read
@@ -143 +143 @@
 type of restart \NEMO\ will write. If it is set to 0, default \NEMO\ functionality will be used - each
 processor writes its own restart file; if it is set to 1 XIOS will write restart into a single file;
-for \np{nn\_wxios}\forcode{ = 2} the restart will be written by XIOS into multiple files, one for each XIOS server.
-Note, however, that \textbf{\NEMO\ will not read restart generated by XIOS when \np{nn\_wxios}\forcode{ = 2}}. The restart will
+for \np{nn\_wxios}\forcode{=2} the restart will be written by XIOS into multiple files, one for each XIOS server.
+Note, however, that \textbf{\NEMO\ will not read restart generated by XIOS when \np{nn\_wxios}\forcode{=2}}. The restart will
 have to be rebuild before continuing the run. This option aims to reduce number of restart files generated by \NEMO\ only,
 and may be useful when there is a need to change number of processors used to run simulation.
@@ -1508 +1508 @@
 \textbf{Note that} in the current version (v3.6), many changes has been introduced but not fully tested.
 In particular, options associated with \np{ln\_dyn\_mxl}, \np{ln\_vor\_trd}, and \np{ln\_tra\_mxl} are not working,
-and none of the options have been tested with variable volume (\ie\ \np{ln\_linssh}\forcode{ = .true.}).
+and none of the options have been tested with variable volume (\ie\ \np{ln\_linssh}\forcode{=.true.}).
 
 % -------------------------------------------------------------------------------------------------------------
@@ -1525 +1525 @@
 Options are defined by \nam{flo} namelist variables.
 The algorithm used is based either on the work of \cite{blanke.raynaud_JPO97} (default option),
-or on a $4^th$ Runge-Hutta algorithm (\np{ln\_flork4}\forcode{ = .true.}).
+or on a $4^th$ Runge-Hutta algorithm (\np{ln\_flork4}\forcode{=.true.}).
 Note that the \cite{blanke.raynaud_JPO97} algorithm have the advantage of providing trajectories which
 are consistent with the numeric of the code, so that the trajectories never intercept the bathymetry.
@@ -1532 +1532 @@
 
 Initial coordinates can be given with Ariane Tools convention
-(IJK coordinates, (\np{ln\_ariane}\forcode{ = .true.}) ) or with longitude and latitude.
+(IJK coordinates, (\np{ln\_ariane}\forcode{=.true.}) ) or with longitude and latitude.
 
 In case of Ariane convention, input filename is \textit{init\_float\_ariane}.
@@ -1583 +1583 @@
 
 \np{jpnfl} is the total number of floats during the run.
-When initial positions are read in a restart file (\np{ln\_rstflo}\forcode{ = .true.} ),
+When initial positions are read in a restart file (\np{ln\_rstflo}\forcode{=.true.} ),
 \np{jpnflnewflo} can be added in the initialization file.
 
@@ -1591 +1591 @@
 creation of the float restart file.
 
-Output data can be written in ascii files (\np{ln\_flo\_ascii}\forcode{ = .true.}).
+Output data can be written in ascii files (\np{ln\_flo\_ascii}\forcode{=.true.}).
 In that case, output filename is trajec\_float.
 
-Another possiblity of writing format is Netcdf (\np{ln\_flo\_ascii}\forcode{ = .false.}) with
+Another possiblity of writing format is Netcdf (\np{ln\_flo\_ascii}\forcode{=.false.}) with
 \key{iomput} and outputs selected in iodef.xml.
 Here it is an example of specification to put in files description section:
@@ -1944 +1944 @@
 
 Third, the discretisation of \autoref{eq:steric_Bq} depends on the type of free surface which is considered.
-In the non linear free surface case, \ie\ \np{ln\_linssh}\forcode{ = .true.}, it is given by
+In the non linear free surface case, \ie\ \np{ln\_linssh}\forcode{=.true.}, it is given by
 
 \[
@@ -2039 +2039 @@
 sea water pressure at sea floor (botpres), dynamic sea surface height (sshdyn).
 
-In \mdl{diaptr} when \np{ln\_diaptr}\forcode{ = .true.}
+In \mdl{diaptr} when \np{ln\_diaptr}\forcode{=.true.}
 (see the \nam{ptr} namelist below) can be computed on-line the poleward heat and salt transports,
 their advective and diffusive component, and the meriodional stream function .
-When \np{ln\_subbas}\forcode{ = .true.}, transports and stream function are computed for the Atlantic, Indian,
+When \np{ln\_subbas}\forcode{=.true.}, transports and stream function are computed for the Atlantic, Indian,
 Pacific and Indo-Pacific Oceans (defined north of 30\deg{S}) as well as for the World Ocean.
 The sub-basin decomposition requires an input file (\ifile{subbasins}) which contains three 2D mask arrays,