Changes between Version 10 and Version 11 of DevelopmentActivities/OasisDriver


Ignore:
Timestamp:
06/17/14 10:19:42 (7 years ago)
Author:
jpolcher
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentActivities/OasisDriver

    v10 v11  
    9494== Configuration of this ORCHIDEE version == 
    9595 
    96 As OASIS does not provide a mechanism to exchange time and grid descriptions between two coupled models some extra information needed to be added to the run.def. Obviously the coupling mechanism itself also needs to be documented in the namecouple of OASIS. 
     96As OASIS does not provide a mechanism to exchange time and grid descriptions between two coupled models some extra information needed to be added to the run.def. Obviously the coupling mechanism itself also needs to be documented in the namcouple of OASIS. 
    9797 
    9898=== Added information in the run.def === 
     
    136136 
    137137 
    138 === The namecouple === 
     138=== The namcouple === 
     139 
     140The namcouple is a configuration file of OASIS and it needs to provide some basic information for the coupling process : 
    139141 
    140142 
     143|| '''OASIS key word''' || '''Description''' || '''Values used for the ORCHIDEE coupling''' || 
     144|| $NFIELDS             || The number of fields described in the second part of the namcouple || 27 || 
     145|| $NBMODEL             || The number of models in this experiment + their names (6 characters) || 2 driver orchid || 
     146|| $RUNTIME             || The total simulated time for this run in seconds || To be filled out by the script launching the simulation and computed from the start and end fdates provided in run.def || 
     147|| $NLOGPRT             ||  Amount of information written to OASIS3-MCT log files (see User Guide)  || 0 || 
     148|| $STRINGS             ||  Description of fields being exchanged ||  ... detailed below || 
     149||                      || 1) Symbolic names for the field as found in the sending model || See table above || 
     150||                      || 2) Symbolic names for the field as found in the receiving model || See table above || 
     151||                      || 3) Index of field in cf_name_table.txt                         || 1 ... not used ? || 
     152||                      || 4) Exchange frequency for the field in seconds                 || completed by a script and using information from the run.def || 
     153||                      || 5) Number of analysis to be performed                          || 1 ... is it used ? || 
     154||                      || 6) Restart input NetCDF file names                             || Name of the file where the data could be written || 
     155||                      || 7)  Field status: EXPORTED, EXPOUT, INPUT, OUTPUT              || EXPORTED in all cases || 
    141156 
     157A sample namcouple is provided . 
    142158 
    143159== Execution of the model coupled to the driver == 
     
    149165where : PEDRIV=1 and PEORCH=$(($NSLOTS-$PEDRIV)), i.e. only one processor is for the driver and all others work on ORCHIDEE. 
    150166 
     167In the execution directory the 3 configuration files presented above need to be present : 
     168 * run.def 
     169 * Grid file with the name given in run.def 
     170 * namcouple 
     171 
     172As in previous version of the off-line version of ORCHIDEE the following files are needed : 
     173 * forcing files as named in run.def 
     174 * Restart files if available 
     175 * Surface description files as needed for the model configuration specified in the run.def 
     176  
     177 
    151178== Execution of the model coupled to WRF == 
     179