Changes between Version 1 and Version 2 of DevelopmentActivities/OasisDriver


Ignore:
Timestamp:
06/02/14 17:03:59 (7 years ago)
Author:
jpolcher
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentActivities/OasisDriver

    v1 v2  
    44 
    55 
    6 == The driver for OASIS == 
     6== The driver for OASIS : driver2oasis.f90 == 
    77 
    8 This code simulates an atmospheric model which would provide provide data for ORCHIDEE through OASIS 
     8This code simulates an atmospheric model which would provide provide data for ORCHIDEE through OASIS. 
     9 
     10As the original ORCHIDEE driver (dim2_driver.f90) is outdated and inflexible it has been redeveloped here. 
     11 
     12For the moment this code only read compressed by gathering forcing files which contain a sufficient amount of meta-data (link to document). 
     13 
     14This code is aimed at running only on one processor. It should not be a limiting factor in the execution time as it only reads once the forcing and then only does some simple time interpolations. Furthermore these interpolations are done while ORCHIDEE runs, i.e. it is not blocked by an oasis_get call. 
    915 
    1016== The fields which OASIS exchanges between the atmosphere and the surface == 
    1117 
    12 == The "main" which controls the ORCHIDEE execution == 
     18== The "main" which controls the ORCHIDEE execution : orchideeoasis.f90 == 
     19 
     20== Execution of the model coupled to the driver == 
     21 
     22As OASIS is linked into both models (driver2oasis and orchideeoasis) the execution of the coupled model is simply achieved  by one mpirun command. It can have the following structure : 
     23 
     24mpirun -n $PEDRIV driver2oasis : -n $PEORCH orchideeoasis 
     25 
     26where : PEDRIV=1 and PEORCH=$(($NSLOTS-$PEDRIV)), i.e. only one processor is for the driver and all others work on ORCHIDEE. 
     27 
     28== Execution of the model coupled to WRF ==