Changeset 9376 for branches/2017/dev_merge_2017/DOC/texfiles/chapters/introduction.tex

Timestamp:

2018-03-06T17:12:34+01:00 (6 years ago)

Author:

nicolasmartin

Message:

Global reorganisation of DOC directory: refactoring & cleaning of TeX source code for readability

File:

• branches/2017/dev_merge_2017/DOC/texfiles/chapters/introduction.tex (modified) (2 diffs)

branches/2017/dev_merge_2017/DOC/texfiles/chapters/introduction.tex

@@ -10 +10 @@
 The Nucleus for European Modelling of the Ocean (\NEMO) is a framework of ocean 
 related engines, namely OPA\footnote{OPA = Oc\'{e}an PArall\'{e}lis\'{e}} for the 
-ocean dynamics and thermodynamics, LIM\footnote{LIM= Louvain)la-neuve Ice 
+ocean dynamics and thermodynamics, LIM\footnote{LIM = Louvain la-neuve Ice 
 Model} for the sea-ice dynamics and thermodynamics, TOP\footnote{TOP = Tracer 
 in the Ocean Paradigm} for the biogeochemistry (both transport (TRP) and sources 
-minus sinks (LOBSTER, PISCES)\footnote{Both LOBSTER and PISCES are not 
-acronyms just name}. It is intended to be a flexible tool for studying the ocean and 
-its interactions with the other components of the earth climate system (atmosphere, 
-sea-ice, biogeochemical tracers, ...) over a wide range of space and time scales. 
+minus sinks (LOBSTER\footnote{LOBSTER = Lodyc Ocean Biogeochemical SysTem for 
+Ecosystem and Resources}, PISCES\footnote{PISCES = Pelagic Interactions Scheme for 
+Carbon and Ecosystem Studies}). It is intended to be a flexible tool for studying 
+the ocean and its interactions with the other components of the earth climate system 
+(atmosphere, sea-ice, biogeochemical tracers, ...) over a wide range of space and time scales. 
 This documentation provides information about the physics represented by the ocean 
 component of \NEMO and the rationale for the choice of numerical schemes and 
@@ -91 +92 @@
 Some CPP keys are implemented in the FORTRAN code to allow code selection at compiling step. This selection of code at compilation time reduces the reliability of the whole platform since it changes the code from one set of CPP keys to the other. It is used only when the addition/suppression of the part of code highly changes the amount of memory at run time.
 Usual coding looks like : 
- \vspace{-10pt}
-\begin{alltt}
-\tiny  
-\begin{verbatim}
-#if defined key_option1    
-             This part of the FORTRAN code will be active   
-             only if key_option1 is activated at compiling step 
-#endif  
-\end{verbatim} 
-\end{alltt}     
-
+\vspace{-10pt}
+\begin{fortrancode}
+#if defined key_option1
+   ! This part of the FORTRAN code will be active
+   ! only if key_option1 is activated at compiling step
+#endif
+\end{fortrancode}
 
 \noindent \index{Namelist} Namelists