Changeset 7705 for trunk/DOC/TexFiles/Chapters/Chap_CFG.tex

Ignore:
Timestamp:
2017-02-21T13:53:54+01:00 (4 years ago)
Message:

update NEMO documentation in trunk

File:
1 edited

Legend:

Unmodified
 r7646 thus allowing the user to verify that the code is performing in a manner consistent with that we are running. This form of verification is critical as one adopts the code for his or her particular research purposes. The test cases also provide a sense for some of the options available research purposes. The reference configurations also provide a sense for some of the options available in the code, though by no means are all options exercised in the reference configurations. Configuration is defined mainly through the \ngn{namcfg} namelist variables: Configuration is defined mainly through the \ngn{namcfg}  namelist variables: \sfcomment {Here change namcfg part of namelist. Configuration is defined throughout domain\_cfg.nc file now} %------------------------------------------namcfg---------------------------------------------------- \namdisplay{namcfg} the LIM sea-ice model (ORCA-LIM) and possibly with PISCES biogeochemical model (ORCA-LIM-PISCES), using various resolutions. The appropriate \textit{\&namcfg} namelist is available in \textit{CONFIG/ORCA2\_LIM/EXP00/namelist\_cfg} for ORCA2 and in \textit{CONFIG/SHARED/README\_other\_configurations\_namelist\_namcfg} The appropriate namelist is available in \textit{CONFIG/ORCA2\_LIM3\_PISCES/EXP00/namelist\_cfg} for ORCA2 and in \textit{CONFIG/SHARED/README\_configs\_namcfg\_namdom}  \sfcomment {not really true, they are obsolete namelists, where find these informations?} for other resolutions The NEMO system is provided with five built-in ORCA configurations which differ in the horizontal resolution. The value of the resolution is given by the resolution at the Equator expressed in degrees. Each of configuration is set through the \textit{\ngn{namcfg}} namelist, which sets the grid size and configuration name parameters  (Tab. \ref{Tab_ORCA}). . expressed in degrees. Each of configuration is set through the \textit{domain\_cfg} file, which sets the grid size and configuration name parameters \sfcomment {I would like to change tab_ORCA but I can not find it, wrong jp_cfg} (Tab. \ref{Tab_ORCA}). %--------------------------------------------------TABLE-------------------------------------------------- \begin{table}[!t]     \begin{center} \begin{tabular}{p{4cm} c c c c} Horizontal Grid                         & \np{jp\_cfg} &  \np{jpiglo} & \np{jpjglo} &       \\ Horizontal Grid                         & \np{ORCA\_index} &  \np{jpiglo} & \np{jpjglo} &       \\ \hline  \hline \~4\deg     &        4         &         92     &      76      &       \\ \caption{ \label{Tab_ORCA} Set of predefined parameters for ORCA family configurations. In all cases, the name of the configuration is set to "orca" ($i.e.$ \np{cp\_cfg}~=~orca). } In all cases, the flag for configurations of ORCA family is set to 1 in \textit{domain\_cfg} } \end{center} \end{table} For ORCA\_R1 and R025, setting the configuration key to 75 allows to use 75 vertical levels, otherwise 46 are used. In the other ORCA configurations, 31 levels are used (see Tab.~\ref{Tab_orca_zgr} and Fig.~\ref{Fig_zgr}). (see Tab.~\ref{Tab_orca_zgr} \sfcomment{HERE I need to put new table for ORCA2 values} and Fig.~\ref{Fig_zgr}). Only the ORCA\_R2 is provided with all its input files in the \NEMO distribution. ORCA\_R2 pre-defined configuration can also be run with an AGRIF zoom over the Agulhas current area ( \key{agrif}  defined) and,  by setting the appropriate variables in \textit{\&namcfg}, see \textit{CONFIG/SHARED/namelist\_ref} current area ( \key{agrif}  defined) and, by setting the appropriate variables, see \textit{CONFIG/SHARED/namelist\_ref} a regional Arctic or peri-Antarctic configuration is extracted from an ORCA\_R2 or R05 configurations using sponge layers at open boundaries. uniformly applied to the whole domain. The GYRE configuration is set through the \textit{\&namcfg} namelist defined in the reference configuration \textit{CONFIG/GYRE/EXP00/namelist\_cfg}. Its horizontal resolution (and thus the size of the domain) is determined by setting \np{jp\_cfg} : \\ \np{jpiglo} $= 30 \times$ \np{jp\_cfg} + 2   \\ \np{jpjglo} $= 20 \times$ \np{jp\_cfg} + 2   \\ The GYRE configuration is set like an analytical configuration, through \np{ln\_read\_cfg\textit{=true}} in \textit{namcfg} namelist defined in the reference configuration \textit{CONFIG/GYRE/EXP00/namelist\_cfg}. Its horizontal resolution (and thus the size of the domain) is determined by setting \np{nn\_GYRE} in  \ngn{namusr\_def}: \\ \np{jpiglo} $= 30 \times$ \np{nn\_GYRE} + 2   \\ \np{jpjglo} $= 20 \times$ \np{nn\_GYRE} + 2   \\ Obviously, the namelist parameters have to be adjusted to the chosen resolution, see the Configurations pages on the NEMO web site (Using NEMO\/Configurations) . its resolution and as it does not requires any input file. For example, keeping a same model size on each processor while increasing the number of processor used is very easy, even though the physical integrity of the solution can be compromised. physical integrity of the solution can be compromised. Benchmark is activate via \np{ln\_bench\textit{=true}} in \ngn{namusr\_def} in namelist  \textit{CONFIG/GYRE/EXP00/namelist\_cfg}. %>>>>>>>>>>>>>>>>>>>>>>>>>>>> %>>>>>>>>>>>>>>>>>>>>>>>>>>>> % ------------------------------------------------------------------------------------------------------------- %       EEL family configuration % ------------------------------------------------------------------------------------------------------------- \section{EEL family: periodic channel} \label{MISC_config_EEL} \begin{description} \item[eel\_r2]  to be described.... \item[eel\_r5] \item[eel\_r6] \end{description} The appropriate \textit{\&namcfg} namelists are available in \textit{CONFIG/SHARED/README\_other\_configurations\_namelist\_namcfg} % ------------------------------------------------------------------------------------------------------------- %       AMM configuration