Ignore:
Timestamp:
2018-03-06T17:12:34+01:00 (2 years ago)
Author:
nicolasmartin
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/2017/dev_merge_2017/DOC/texfiles/chapters/introduction.tex

    r9373 r9376  
    1010The Nucleus for European Modelling of the Ocean (\NEMO) is a framework of ocean  
    1111related engines, namely OPA\footnote{OPA = Oc\'{e}an PArall\'{e}lis\'{e}} for the  
    12 ocean dynamics and thermodynamics, LIM\footnote{LIM= Louvain)la-neuve Ice  
     12ocean dynamics and thermodynamics, LIM\footnote{LIM = Louvain la-neuve Ice  
    1313Model} for the sea-ice dynamics and thermodynamics, TOP\footnote{TOP = Tracer  
    1414in the Ocean Paradigm} for the biogeochemistry (both transport (TRP) and sources  
    15 minus sinks (LOBSTER, PISCES)\footnote{Both LOBSTER and PISCES are not  
    16 acronyms just name}. It is intended to be a flexible tool for studying the ocean and  
    17 its interactions with the other components of the earth climate system (atmosphere,  
    18 sea-ice, biogeochemical tracers, ...) over a wide range of space and time scales.  
     15minus sinks (LOBSTER\footnote{LOBSTER = Lodyc Ocean Biogeochemical SysTem for  
     16Ecosystem and Resources}, PISCES\footnote{PISCES = Pelagic Interactions Scheme for  
     17Carbon and Ecosystem Studies}). It is intended to be a flexible tool for studying  
     18the ocean and its interactions with the other components of the earth climate system  
     19(atmosphere, sea-ice, biogeochemical tracers, ...) over a wide range of space and time scales.  
    1920This documentation provides information about the physics represented by the ocean  
    2021component of \NEMO and the rationale for the choice of numerical schemes and  
     
    9192Some 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. 
    9293Usual coding looks like :  
    93  \vspace{-10pt} 
    94 \begin{alltt} 
    95 \tiny   
    96 \begin{verbatim} 
    97 #if defined key_option1     
    98              This part of the FORTRAN code will be active    
    99              only if key_option1 is activated at compiling step  
    100 #endif   
    101 \end{verbatim}  
    102 \end{alltt}      
    103  
     94\vspace{-10pt} 
     95\begin{fortrancode} 
     96#if defined key_option1 
     97   ! This part of the FORTRAN code will be active 
     98   ! only if key_option1 is activated at compiling step 
     99#endif 
     100\end{fortrancode} 
    104101 
    105102\noindent \index{Namelist} Namelists 
Note: See TracChangeset for help on using the changeset viewer.