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 9019 for branches/2017/dev_merge_2017/DOC/TexFiles/Chapters/Chap_MISC.tex – NEMO

Ignore:
Timestamp:
2017-12-13T15:58:53+01:00 (6 years ago)
Author:
timgraham
Message:

Merge of dev_CNRS_2017 into branch

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/2017/dev_merge_2017/DOC/TexFiles/Chapters/Chap_MISC.tex

    r7646 r9019  
    22\begin{document} 
    33% ================================================================ 
    4 % Chapter ——— Miscellaneous Topics 
     4% Chapter ---€” Miscellaneous Topics 
    55% ================================================================ 
    66\chapter{Miscellaneous Topics} 
     
    8787 
    8888% ================================================================ 
    89 % Sub-Domain Functionality (\textit{nizoom, njzoom}, namelist parameters) 
    90 % ================================================================ 
    91 \section{Sub-Domain Functionality (\np{jpizoom}, \np{jpjzoom})} 
     89% Sub-Domain Functionality  
     90% ================================================================ 
     91\section{Sub-Domain Functionality} 
    9292\label{MISC_zoom} 
    93  
    94 The sub-domain functionality, also improperly called the zoom option  
    95 (improperly because it is not associated with a change in model resolution)  
    96 is a quite simple function that allows a simulation over a sub-domain of an  
    97 already defined configuration ($i.e.$ without defining a new mesh, initial  
    98 state and forcings). This option can be useful for testing the user settings  
    99 of surface boundary conditions, or the initial ocean state of a huge ocean  
    100 model configuration while having a small computer memory requirement.  
    101 It can also be used to easily test specific physics in a sub-domain (for example,  
    102 see \citep{Madec_al_JPO96} for a test of the coupling used in the global ocean  
    103 version of OPA between sea-ice and ocean model over the Arctic or Antarctic  
    104 ocean, using a sub-domain). In the standard model, this option does not  
    105 include any specific treatment for the ocean boundaries of the sub-domain:  
    106 they are considered as artificial vertical walls. Nevertheless, it is quite easy  
    107 to add a restoring term toward a climatology in the vicinity of such boundaries  
    108 (see \S\ref{TRA_dmp}). 
    109  
    110 In order to easily define a sub-domain over which the computation can be  
    111 performed, the dimension of all input arrays (ocean mesh, bathymetry,  
    112 forcing, initial state, ...) are defined as \np{jpidta}, \np{jpjdta} and \np{jpkdta}  
    113 ( in \ngn{namcfg} namelist), while the computational domain is defined through  
    114 \np{jpiglo}, \np{jpjglo} and \jp{jpk} (\ngn{namcfg} namelist). When running the  
    115 model over the whole domain, the user sets \np{jpiglo}=\np{jpidta} \np{jpjglo}=\np{jpjdta}  
    116 and \jp{jpk}=\jp{jpkdta}. When running the model over a sub-domain, the user  
    117 has to provide the size of the sub-domain, (\np{jpiglo}, \np{jpjglo}, \np{jpkglo}),  
    118 and the indices of the south western corner as \np{jpizoom} and \np{jpjzoom} in  
    119 the  \ngn{namcfg} namelist (Fig.~\ref{Fig_LBC_zoom}).  
    120  
    121 Note that a third set of dimensions exist, \jp{jpi}, \jp{jpj} and \jp{jpk} which is  
    122 actually used to perform the computation. It is set by default to \jp{jpi}=\np{jpjglo}  
    123 and \jp{jpj}=\np{jpjglo}, except for massively parallel computing where the  
    124 computational domain is laid out on local processor memories following a 2D  
    125 horizontal splitting. % (see {\S}IV.2-c) ref to the section to be updated 
    12693 
    12794\subsection{Simple subsetting of input files via netCDF attributes} 
     
    165132\noindent Add the logical switch to \ngn{namcfg} in the configuration namelist and set true: 
    166133%--------------------------------------------namcfg-------------------------------------------------------- 
    167 \namdisplay{namcfg_orca1} 
     134\namdisplay{namcfg} 
    168135%-------------------------------------------------------------------------------------------------------------- 
    169136 
Note: See TracChangeset for help on using the changeset viewer.