New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
Changeset 3989 for branches/2013/dev_r3853_CNRS9_ConfSetting/DOC/TexFiles/Chapters/Introduction.tex – NEMO

Ignore:
Timestamp:
2013-07-24T11:48:35+02:00 (11 years ago)
Author:
clevy
Message:

Configuration setting/Step3 and doc, see ticket:#1074

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/2013/dev_r3853_CNRS9_ConfSetting/DOC/TexFiles/Chapters/Introduction.tex

    r3625 r3989  
    8181the coefficients with \citet{Blanke1993}, \citet{Large_al_RG94}, \citet{Pacanowski_Philander_JPO81},  
    8282or \citet{Umlauf_Burchard_JMS03} mixing schemes. 
     83 \vspace{1cm} 
     84  
     85  
     86\noindent CPP keys and namelists are used for inputs to the code.  \newline 
     87 
     88\noindent \index{CPP keys} CPP keys \newline 
     89Some 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. 
     90Usual coding looks like :  
     91 \vspace{-10pt} 
     92\begin{alltt} 
     93\tiny   
     94\begin{verbatim} 
     95#if defined key_option1     
     96             This part of the FORTRAN code will be active    
     97             only if key_option1 is activated at compiling step  
     98#endif   
     99\end{verbatim}  
     100\end{alltt}      
     101 
     102 
     103\noindent \index{Namelist} Namelists 
     104 
     105The namelist allows to input variables (character, logical, real and integer) into the code. There is one namelist file for each component of NEMO (dynamics, sea-ice, biogeochemistry...) containing all the FOTRAN namelists needed. The implementation in NEMO uses a two step process. For each FORTRAN namelist, two files are read: 
     106\begin{enumerate} 
     107\item A reference namelist ( in \textit{CONFIG/SHARED/namelist\_ref} ) is read first. This file contains all the namelist variables which are initialised to default values   
     108\item A configuration namelist ( in \textit{CONFIG/CFG\_NAME/EXP00/namelist\_cfg} ) is read aferwards. This file contains only the namelist variables which are changed from default values, and overwrites those. 
     109\end{enumerate} 
     110A template can be found in \textit{NEMO/OPA\_SRC/module.example} 
     111The effective namelist, taken in account during the run, is stored at execution time in an output\_namelist\_dyn (or \_ice or \_top) file. 
     112 \vspace{1cm} 
     113 
    83114 
    84115Model outputs management and specific online diagnostics are described in chapters~\ref{DIA}. 
Note: See TracChangeset for help on using the changeset viewer.