New URL for NEMO forge!

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.
Users/ModelInterfacing/InputsOutputs (diff) – NEMO

Changes between Version 1 and Version 2 of Users/ModelInterfacing/InputsOutputs

2017-03-01T16:32:28+01:00 (7 years ago)



  • Users/ModelInterfacing/InputsOutputs

    v1 v2  
    1 = Inputs-Outputs (XIOS) 
     1= Inputs-Outputs (Using XIOS) 
     3Output of diagnostics in NEMO is usually done using XIOS. This is an efficient way of writing diagnostics because the time averaging, file writing and even some simple arithmetic or regridding is carried out in parallel to the NEMO model run. This page gives a basic introduction to using XIOS with NEMO. Much more information is available from the XIOS homepage above. 
     5Use of XIOS for diagnostics is activated using the pre-compiler key "key_iomput". In nemo_v3_6_STABLE the default version of XIOS is XIOS1.0 but XIOS2.0 can be used by activating key_xios2. '''NB: Due to a change in the XIOS1.0 branch NEMO v3.6 STABLE will only work up to revision 703 of the XIOS1.0 branch.''' At the head of the NEMO trunk only XIOS2.0 can be used (XIOS2.0 is the XIOS trunk) and key_xios2 is not required. 
     7== XIOS namelists == 
     8XIOS is controlled using xml input files. Examples of these files can be found in the reference configurations (NEMOGCM/CONFIG). The XIOS executable expects to find a file called iodef.xml in the model run directory. In NEMO we have made the decision to use include statements in the iodef.xml file to include field_def.xml and domain_def.xml from the NEMOGCM/CONFIG/SHARED directory. Most users will not need to modify domain_def.xml or field_def.xml unless they want to add new diagnostics to the NEMO code. 
     10In the nemo trunk the field_def.xml file has been further split into field_def-opa.xml (for physics), field_def-lim.xml (for ice) and field_def-bgc.xml (for biogeochemistry). Also the definition of the outpu 
     11t files has been moved from the iodef.xml file into separate file_definition.xml files which are included in the iodef.xml file. 
     14== XIOS modes == 
     15=== Detached Mode === 
     16In detached mode the XIOS executable is executed on separate cores from the NEMO model. This is the recommended method for using XIOS for realistic model runs. To use this mode set "using_server" to true at 
     17the bottom of the iodef.xml file. Make sure there is a copy (or link to) your XIOS execuatble in the working directory and in your job submission script allocate processors to XIOS. 
     19=== Attached Mode === 
     20In attached mode XIOS runs on each of the cores used by NEMO. This method is less efficient than the detached mode but can be more convenient for testing or with small configurations. To activate this mode simply set "using_server" to false in the iodef.xml file and don't allocate any cores to XIOS. Note that due to the different domain decompositions between XIOS and NEMO if the total number of cores is larger than the number of grid points in the j direction then the model run will fail.