- Timestamp:
- 2017-12-13T15:58:53+01:00 (6 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/2017/dev_merge_2017/DOC/TexFiles/Chapters/Chap_MISC.tex
r7646 r9019 2 2 \begin{document} 3 3 % ================================================================ 4 % Chapter ———Miscellaneous Topics4 % Chapter --- Miscellaneous Topics 5 5 % ================================================================ 6 6 \chapter{Miscellaneous Topics} … … 87 87 88 88 % ================================================================ 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} 92 92 \label{MISC_zoom} 93 94 The sub-domain functionality, also improperly called the zoom option95 (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 an97 already defined configuration ($i.e.$ without defining a new mesh, initial98 state and forcings). This option can be useful for testing the user settings99 of surface boundary conditions, or the initial ocean state of a huge ocean100 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 ocean103 version of OPA between sea-ice and ocean model over the Arctic or Antarctic104 ocean, using a sub-domain). In the standard model, this option does not105 include any specific treatment for the ocean boundaries of the sub-domain:106 they are considered as artificial vertical walls. Nevertheless, it is quite easy107 to add a restoring term toward a climatology in the vicinity of such boundaries108 (see \S\ref{TRA_dmp}).109 110 In order to easily define a sub-domain over which the computation can be111 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 through114 \np{jpiglo}, \np{jpjglo} and \jp{jpk} (\ngn{namcfg} namelist). When running the115 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 user117 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} in119 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 is122 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 the124 computational domain is laid out on local processor memories following a 2D125 horizontal splitting. % (see {\S}IV.2-c) ref to the section to be updated126 93 127 94 \subsection{Simple subsetting of input files via netCDF attributes} … … 165 132 \noindent Add the logical switch to \ngn{namcfg} in the configuration namelist and set true: 166 133 %--------------------------------------------namcfg-------------------------------------------------------- 167 \namdisplay{namcfg _orca1}134 \namdisplay{namcfg} 168 135 %-------------------------------------------------------------------------------------------------------------- 169 136
Note: See TracChangeset
for help on using the changeset viewer.