Changeset 10509 for NEMO/trunk
- Timestamp:
- 2019-01-14T11:09:05+01:00 (5 years ago)
- Location:
- NEMO/trunk/doc/latex/NEMO
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
NEMO/trunk/doc/latex/NEMO/main/NEMO_manual.tex
r10495 r10509 46 46 \Large Gurvan Madec and NEMO System Team 47 47 \thanks{ 48 Yevgeny Aksenov, Mire ck Andrejczuk, Mike Bell, Romain Bourdalle-Badie, Cl\'{e}ment Bricaud,48 Yevgeny Aksenov, Mirek Andrejczuk, Mike Bell, Romain Bourdalle-Badie, Cl\'{e}ment Bricaud, 49 49 J\'{e}r\^{o}me Chanut, Stefania Ciliberti, Emanuela Clementi, Andrew Coward, Damiano Delrosso, 50 50 Massimiliano Drudi, Christian Eth\'{e}, Simona Flavoni, Doroteaciro Iovino, Claire L\'{e}vy, Tomas Lovato, -
NEMO/trunk/doc/latex/NEMO/subfiles/chap_DIA.tex
r10442 r10509 115 115 Note that for smaller configurations, the rebuilding phase can be avoided, 116 116 even without a parallel-enabled NetCDF4 library, simply by employing only one dedicated I/O server. 117 118 \subsection{XIOS: Reading and writing restart file} 119 120 XIOS may be used to read single file restart produced by NEMO. Currently only the variables written to 121 file \forcode{numror} can be handled by XIOS. To activate restart reading using XIOS, set \np{ln\_xios\_read}\forcode{ = .true. } 122 in \textit{namelist\_cfg}. This setting will be ignored when multiple restart files are present, and default NEMO 123 functionality will be used for reading. There is no need to change iodef.xml file to use XIOS to read 124 restart, all definitions are done within the NEMO code. For high resolution configuration, however, 125 there may be a need to add the following line in iodef.xml (xios context): 126 127 \begin{xmllines} 128 <variable id="recv_field_timeout" type="double">1800</variable> 129 \end{xmllines} 130 131 This variable sets timeout for reading. 132 133 If XIOS is to be used to read restart from file generated with an earlier NEMO version (3.6 for instance), 134 dimension \forcode{z} defined in restart file must be renamed to \forcode{nav_lev}.\\ 135 136 XIOS can also be used to write NEMO restart. A namelist parameter \np{nn\_wxios} is used to determine the 137 type of restart NEMO will write. If it is set to 0, default NEMO functionality will be used - each 138 processor writes its own restart file; if it is set to 1 XIOS will write restart into a single file; 139 for \np{nn\_wxios = 2} the restart will be written by XIOS into multiple files, one for each XIOS server. 140 Note, however, that \textbf{NEMO will not read restart generated by XIOS when \np{nn\_wxios = 2}}. The restart will 141 have to be rebuild before continuing the run. This option aims to reduce number of restart files generated by NEMO only, 142 and may be useful when there is a need to change number of processors used to run simulation. 143 144 If an additional variable must be written to a restart file, the following steps are needed: 145 \begin{description} 146 \item[step 1:] add variable name to a list of restart variables (in subroutine \rou{iom\_set\_rst\_vars,} \mdl{iom}) and 147 define correct grid for the variable (\forcode{grid_N_3D} - 3D variable, \forcode{grid_N} - 2D variable, \forcode{grid_vector} - 148 1D variable, \forcode{grid_scalar} - scalar), 149 \item[step 2:] add variable to the list of fields written by restart. This can be done either in subroutine 150 \rou{iom\_set\_rstw\_core} (\mdl{iom}) or by calling \rou{iom\_set\_rstw\_active} (\mdl{iom}) with the name of a variable 151 as an argument. This convention follows approach for writing restart using iom, where variables are 152 written either by \rou{rst\_write} or by calling \rou{iom\_rstput} from individual routines. 153 \end{description} 154 155 156 An older versions of XIOS do not support reading functionality. It's recommended to use at least XIOS2@1451. 157 117 158 118 159 \subsection{XIOS: XML Inputs-Outputs Server}
Note: See TracChangeset
for help on using the changeset viewer.