# Changeset 11552

Ignore:
Timestamp:
2019-09-16T17:38:22+02:00 (13 months ago)
Message:

add unbreakable space after \fortran & fninety

Location:
NEMO/trunk/doc/latex/NEMO/subfiles
Files:
6 edited

Unmodified
Added
Removed
• ## NEMO/trunk/doc/latex/NEMO/subfiles/chap_DOM.tex

 r11543 \caption{ \protect\label{fig:DOM_index_hor} Horizontal integer indexing used in the \fortran code. Horizontal integer indexing used in the \fortran\ code. The dashed area indicates the cell in which variables contained in arrays have the same $i$- and $j$-indices } %>>>>>>>>>>>>>>>>>>>>>>>>>>>> The array representation used in the \fortran code requires an integer indexing. The array representation used in the \fortran\ code requires an integer indexing. However, the analytical definition of the mesh (see \autoref{subsec:DOM_cell}) is associated with the use of integer values for $t$-points only while all the other points involve integer and a half values. In the vertical, the chosen indexing requires special attention since the direction of the $k$-axis in the \fortran code is the reverse of that used in the semi -discrete equations and the \fortran\ code is the reverse of that used in the semi -discrete equations and given in \autoref{subsec:DOM_cell}. The sea surface corresponds to the $w$-level $k = 1$, which is the same index as the $t$-level just below (compare the dashed area in \autoref{fig:DOM_index_hor} and \autoref{fig:DOM_index_vert}). Since the scale factors are chosen to be strictly positive, a \textit{minus sign} is included in the \fortran implementations of a \textit{minus sign} is included in the \fortran\ implementations of \textit{all the vertical derivatives} of the discrete equations given in this manual in order to accommodate the opposing vertical index directions in implementation and documentation. \caption{ \protect\label{fig:DOM_index_vert} Vertical integer indexing used in the \fortran code. Vertical integer indexing used in the \fortran\ code. Note that the $k$-axis is oriented downward. The dashed area indicates the cell in which variables contained in arrays have a common $k$-index.
• ## NEMO/trunk/doc/latex/NEMO/subfiles/chap_DYN.tex

 r11543 its physical meaning is not the same: in the second case, $w$ is the velocity normal to the $s$-surfaces. Note also that the $k$-axis is re-orientated downwards in the \fortran code compared to Note also that the $k$-axis is re-orientated downwards in the \fortran\ code compared to the indexing used in the semi-discrete equations such as \autoref{eq:DYN_wzv} (see \autoref{subsec:DOM_Num_Index_vertical}).
• ## NEMO/trunk/doc/latex/NEMO/subfiles/chap_LBC.tex

 r11551 These restrictions mean that data files used with versions of the model prior to Version 3.4 may not work with Version 3.4 onwards. A \fortran utility {\itshape bdy\_reorder} exists in the TOOLS directory which A \fortran\ utility {\itshape bdy\_reorder} exists in the TOOLS directory which will re-order the data in old BDY data files.
• ## NEMO/trunk/doc/latex/NEMO/subfiles/chap_OBS.tex

 r11543 For convenience some tools for viewing and processing of observation and feedback files are provided in the \NEMO\ repository. These tools include OBSTOOLS which are a collection of \fortran programs which are helpful to deal with feedback files. These tools include OBSTOOLS which are a collection of \fortran\ programs which are helpful to deal with feedback files. They do such tasks as observation file conversion, printing of file contents, some basic statistical analysis of feedback files. \subsection{Obstools} A series of \fortran utilities is provided with \NEMO\ called OBSTOOLS. A series of \fortran\ utilities is provided with \NEMO\ called OBSTOOLS. This are helpful in handling observation files and the feedback file output from the observation operator. A brief description of some of the utilities follows
• ## NEMO/trunk/doc/latex/NEMO/subfiles/chap_TRA.tex

 r11543 The coefficients are a polynomial function of temperature, salinity and depth which expression depends on the chosen EOS. They are computed through \textit{eos\_rab}, a \fortran function that can be found in \mdl{eosbn2}. They are computed through \textit{eos\_rab}, a \fortran\ function that can be found in \mdl{eosbn2}. % ------------------------------------------------------------------------------------------------------------- thus the pressure dependent terms in \autoref{eq:TRA_eos_fzp} (last term) have been dropped. The freezing point is computed through \textit{eos\_fzp}, a \fortran function that can be found in \mdl{eosbn2}. a \fortran\ function that can be found in \mdl{eosbn2}. % -------------------------------------------------------------------------------------------------------------
• ## NEMO/trunk/doc/latex/NEMO/subfiles/chap_misc.tex

 r11543 configuration using the extended grid domain configuration file: \ifile{eORCA1\_domcfg.nc} This file define a horizontal domain of 362x332.  The first row with open ocean wet points in the non-isf bathymetry for this set is row 42 (\fortran indexing) open ocean wet points in the non-isf bathymetry for this set is row 42 (\fortran\ indexing) then the formally correct setting for \np{open\_ocean\_jstart} is 41.  Using this value as the first row to be read will result in a 362x292 domain which is the same size as the \label{subsec:MISC_sign} The SIGN(A, B) is the \fortran intrinsic function delivers the magnitude of A with the sign of B. The SIGN(A, B) is the \fortran\ intrinsic function delivers the magnitude of A with the sign of B. For example, SIGN(-3.0,2.0) has the value 3.0. The problematic case is when the second argument is zero, because, on platforms that support IEEE arithmetic, and the processor is capable of distinguishing between positive and negative zero, and B is negative real zero. Then SIGN delivers a negative result where, under \fninety rules, it used to return a positive result. Then SIGN delivers a negative result where, under \fninety\ rules, it used to return a positive result. This change may be especially sensitive for the ice model, so we overwrite the intrinsinc function with our own function simply performing :   \\
Note: See TracChangeset for help on using the changeset viewer.