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 11734 for NEMO/trunk/cfgs/SHARED – NEMO

Ignore:
Timestamp:
2019-10-18T18:46:26+02:00 (5 years ago)
Author:
nicolasmartin
Message:

Review README for reference confgiurations

File:
1 edited

Legend:

Unmodified
Added
Removed
  • NEMO/trunk/cfgs/SHARED/README.rst

    r10598 r11734  
    33*********** 
    44 
     5.. todo:: 
     6 
     7 
     8 
    59.. contents:: 
    6            :local: 
     10   :local: 
    711 
    812Output of diagnostics in NEMO is usually done using XIOS. 
     
    1115Much more information is available from the XIOS homepage above and from the NEMO manual. 
    1216 
    13 Use of XIOS for diagnostics is activated using the pre-compiler key ``key_iomput``.  
     17Use of XIOS for diagnostics is activated using the pre-compiler key ``key_iomput``. 
    1418 
    1519Extracting and installing XIOS 
     
    1923   If you want to use single file output you will need to compile the HDF & NetCDF libraries to allow parallel IO. 
    20242. Download the version of XIOS that you wish to use. The recommended version is now XIOS 2.5: 
    21     
     25 
    2226.. code-block:: console 
    2327 
     
    2529 
    2630and follow the instructions in `XIOS documentation <http://forge.ipsl.jussieu.fr/ioserver/wiki/documentation>`_ to compile it. 
    27    If you find problems at this stage, support can be found by subscribing to the `XIOS mailing list <http://forge.ipsl.jussieu.fr/mailman/listinfo.cgi/xios-users>`_ and sending a mail message to it.  
     31   If you find problems at this stage, support can be found by subscribing to the `XIOS mailing list <http://forge.ipsl.jussieu.fr/mailman/listinfo.cgi/xios-users>`_ and sending a mail message to it. 
    2832 
    2933XIOS Configuration files 
     
    73771. Add any necessary code to calculate you new diagnostic in NEMO 
    74782. Send the field to XIOS using ``CALL iom_put( 'field_id', variable )`` where ``field_id`` is a unique id for your new diagnostics and variable is the fortran variable containing the data. 
    75    This should be called at every model timestep regardless of how often you want to output the field. No time averaging should be done in the model code.  
     79   This should be called at every model timestep regardless of how often you want to output the field. No time averaging should be done in the model code. 
    76803. If it is computationally expensive to calculate your new diagnostic you should also use "iom_use" to determine if it is requested in the current model run. For example, 
    77     
     81 
    7882.. code-block:: fortran 
    7983 
Note: See TracChangeset for help on using the changeset viewer.