Changes between Version 20 and Version 21 of Branches/Driver_Improvements

Timestamp:

2016-05-27T12:16:26+02:00 (8 years ago)

Author:

jpolcher

Comment:

--

Branches/Driver_Improvements

@@ -35 +35 @@
 === Jan's understanding of the working of dim2driver (Jan 26/05/2016) ===
 
-It is important to understand that readim2.f90 is written in time steps and not physical time. There are 2 time stepping in the driver :
+It is important to understand that readim2.f90 is written in time steps and not physical time. There are 2 time step counters in the driver :
 - ''n'' : is the list of indices of the time axis in the forcing file and readdim2.f90 will step from n-1 to n.
 - ''itau'' : is the time stepping of ORCHIDEE and takes 'split' values between n-1 and n.
 
-The readdim2.f90 will then interpolate using values at ''n-1'' and ''n'' to obtain the forcing at ''itauin'', which is the current time step of ORCHIDEE. Once ''itau'' has stepped through ''split'' values the forcing values of ''n'' will be copied to ''n-1'' and the new values for ''n'' will be read from the netCDF file.
+The readdim2.f90 will then interpolate using values at ''n-1'' and ''n'' to obtain the forcing at ''itauin'', which is the current time step of ORCHIDEE. Once ''itau'' has stepped through ''split'' values, the forcing values of ''n'' will be copied to ''n-1'' and the new values for ''n'' will be read from the netCDF file.
+Because of this time-step approach the physical time chosen at ''n=1'' is very important.
 
 All this is done independently from the physical time for which the values of the forcing at ''n-1'' and ''n'' are valid over. This poses no problem for instantaneous variables in the forcing file as then the indexing space (''n'') and the physical time are identical.