Changes between Version 3 and Version 4 of DevelopmentActivities/ORCHIDEE-ROUTING


Ignore:
Timestamp:
2020-10-11T15:23:12+02:00 (4 years ago)
Author:
peylin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentActivities/ORCHIDEE-ROUTING

    v3 v4  
    99Participant: Jan P., Anthony S. (from Argentina), Agnes D., Catherine O., Olivier B., Jerome S., Yan M., Thomas D., Emmanuel M., Olivier DM, Philippe P. 
    1010 
    11 Jan and Anthony gave a presentation on the recent progresses about the developement of their new routing scheme and the overall procedure to create the necessary input files for the routing in ORCHIDEE: [attachment: Routage_Jan_Presentation_Oct2020_VAS.pdf Routage_progress_Oct2020] 
     11Jan and Anthony gave a presentation on the recent progresses about the developement of their new routing scheme and the overall procedure to create the necessary input files for the routing scheme in ORCHIDEE: [attachment: Routage_Jan_Presentation_Oct2020_VAS.pdf Routage_progress_Oct2020] 
    1212 
    13 Note that developments for this new routing branche are stored under the ipsl gitlab: https://gitlab.in2p3.fr/ipsl/lmd/intro/routingpp  
     13Note that the developments for this new routing branche are stored under the ipsl gitlab: https://gitlab.in2p3.fr/ipsl/lmd/intro/routingpp  
    1414 
    1515Main actions / points discussed are 
    16  - The need to test/update routing_PP (pre-processor) in order to work with icosaedric grid (especially for the number of neighbours) 
    17  - Potentially test the "efficiency" of routing_PP with a very large number of processor to gain speed (currently several hours in one node for a regional configuration) 
    18  - NEED to test the routing scheme in ORCHIDEE with respect to the intrinsic and numerical properties of the scheme in order to better understand why the results seems to critically depend on the time step in routing and possibly on the number of HTU (hydrological Transfert Units) per grid box (a parameter that can be chosen), etc... For that  
    19   - Need to check/update the "force_routing" program in order to do simple test with a uniq input (drainage and runoff) pre-calculated by ORC. 
    20   - Need to do some elementary tests on the different configuration for the time step, the choise of the initial high resolution description of the basins, etc 
    21   - Yan suggest 
    22   - EM suggest to  
    23  - Agnes wans to contr 
    24       
     16 - Construction of the Hydrological Transfer Units (HTUs) done offline with the pre-processing routing: Routing_PP  
     17  - Need to test/update routing_PP in order to work with icosaedric grid (especially for the number of neighbours) 
     18  - Potentially test the "efficiency" of routing_PP with a very large number of processor to gain speed (currently several hours in one node for a regional configuration) 
     19  - Test the impact of the max number of HTUs per grid cell on the overall routing scheme  
     20 - Routing scheme in ORCHIDEE 
     21  - NEED to test the intrinsic and numerical properties of the scheme in order to better understand why the results (river discharge for the Amazon river at Obidos) seems to critically depend on the time step in routing and possibly on the number of HTUs per grid box, etc... For that a specific "unitary" test with a pulse of rain (or runoff) can be done.  
     22  - To ease the different "unitary test" Jan will update the "force_routing" routine in order to perform some tests with allways the same inputs of water. 
     23  - Agnes also suggested to test the mumeric of the routing scheme with only the "river reservoir"  
     24==> Different tests on the time step, the choise of the HTUs max per grid, the calculation of the topoindex, etc to be done 
     25 - Several people want to help / contribute 
     26  - Agnes wants to apply the scheme for the Seine river basin 
     27  - Thomas will help with the icosaedric grid for routing_pp 
     28  - Emannuel can advise on the numerics 
     29  - Yan will help with respect to reproducing / understanding the difference between routing the water at the highest resolution (using the original basin description from Hydroshed for instance) and the routing a coarser ORCH model resolution.     
    2530 - Next big step will be to parallelise "routing.f90"  
    2631  - Yan will be able to help with XIOS to compute the Halo for each domains, given that the conectivities are pre-calculated by "routing_PP" 
    27    
     32   
    2833 
    2934== Meeting 18 Fevrier 2019 == 
     
    3136Participant: Jan P., Anthony S., Agnes D., Catherine O., Yan M., Thomas D., Olivier DM, Philippe P. 
    3237 
    33 First meeting to discuss the strategy of further developping the routing scheme in ORCHIDEE. 
     38First meeting to discuss the strategy of the developments of the routing scheme in ORCHIDEE. 
    3439 
    3540 - Jan P. presented the approach he is currently following: [attachment: TowardsParallelRouting.pdf Routage_JanP_Fev2019] 
    36  - Yan M. presented his approach which is to perform the routing on a regular lat/lon grid at high resolution (which is easy to parallelise) and to perform some interpolation of the fluxes. 
     41 - Yan M. presented a parallele approach which is to perform the routing on a regular lat/lon grid at high resolution, which is easier to parallelise; the scheme then involve to interpolate of the fluxes to the regular grid. 
    3742  
    3843