Changes between Version 5 and Version 6 of DevelopmentActivities/ORCHIDEE-ROUTING

Timestamp:

2020-10-11T19:05:58+02:00 (4 years ago)

Author:

peylin

Comment:

--

DevelopmentActivities/ORCHIDEE-ROUTING

@@ -15 +15 @@
 Main actions / points discussed are:
  - Construction of the Hydrological Transfer Units (HTUs) done offline with the pre-processing routing: Routing_PP 
-  - Need to test/update routing_PP in order to work with icosaedric grid (especially for the number of neighbours)
+  - Need to test/update routing_PP in order to work with the icosaedric grid (especially for the number of neighbours)
   - 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)
-  - Test the impact of the max number of HTUs per grid cell on the overall routing scheme 
+  - Test the impact of the maximum number of HTUs per grid cell on the overall routing scheme  
  - Routing scheme in ORCHIDEE
-  - 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. 
-  - 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.
-  - Agnes also suggested to test the mumeric of the routing scheme with only the "river reservoir" 
-==> Different tests on the time step, the choise of the HTUs max per grid, the calculation of the topoindex, etc to be done
+  - NEED to test the intrinsic/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) should be done. To ease this approach Jan will update the "force_routing" routine in order to perform some tests with allways the same inputs of water.
+  - Agnes also suggested to test the properties of the routing scheme with only the "river reservoir" 
+==> Different tests on the choise of time step, the choise of the HTUs max per grid, the calculation of the topoindex, etc need to be done!
  - Contributions to this work
-  - Agnes wants to apply the scheme for the Seine river basin
-  - Thomas will help with the icosaedric grid for routing_pp
-  - Emannuel can advise on the numerics
-  - 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.    
+  - Agnes wants to apply the scheme for the Seine river basin to test its properties
+  - Thomas will help with the icosaedric grid to test routing_pp
+  - Emannuel can advise on the numerical problems
+  - 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 routing the water at a coarser ORCH model resolution.    
  - Next big step will be to parallelise "routing.f90" 
-  - 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"
+  - Yan will be able to help with XIOS to compute the Halo for each domain, given that the conectivities are pre-calculated by "routing_PP"
   
 [[BR]]