Changes between Version 13 and Version 14 of DevelopmentActivities/OasisDriver


Ignore:
Timestamp:
12/08/15 11:10:47 (5 years ago)
Author:
nvuilsce
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentActivities/OasisDriver

    v13 v14  
    44Today ORCHIDEE is designed to be called by a subroutine independently on each processor. This is implemented for instance in the traditional off-line driver (dim2_driver.f90) : 
    55 
    6 [[Image(wiki:OasisDriver:Witout_OASIS.png, 350px)]] 
     6[[Image(wiki:DevelopmentActivities/OasisDriver:Witout_OASIS.png, 350px)]] 
    77 
    88This assumes that the domain decomposition of the atmospheric model (or the driver) and ORCHIDEE are the same. It also means that the processors which have no land point to deal with are waiting for the others to finish. 
     
    1010In order to avoid these issues and generalise the coupling of ORCHIDEE with other atmospheric components, the OASIS-MCT coupler can be used. In this case the atmosphere can work on any number of processors and ORCHIDEE on a distinct set of processors. This is exemplified in the driver2oasis presented below. Here, the driver (driver2oasis.f90) which mimics the atmosphere, is a single processor code which just reads some forcing files and provides that data to OASIS. It is a prototype for any atmospheric model which would send the same fields from its n processors to OASIS. 
    1111 
    12 [[Image(wiki:OasisDriver:With_OASIS.png, 350px)]] 
     12[[Image(wiki:DevelopmentActivities/OasisDriver:With_OASIS.png, 350px)]] 
    1313 
    1414In the OASIS approach to coupling, a number of advantages are gained :