Changes between Version 15 and Version 16 of Branches/Driver_Improvements


Ignore:
Timestamp:
2016-05-27T08:49:17+02:00 (8 years ago)
Author:
jpolcher
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Branches/Driver_Improvements

    v15 v16  
    3636 
    3737It is important to understand that readim2.f90 is written in time steps and not physical time. There are 2 time stepping in the driver : 
    38 - n : is the list of indices of the time axis in the forcing file and readdim2.f90 will step from n-1 to n. 
    39 - itau : is the time stepping of ORCHIDEE and takes 'split' values between n-1 and n. 
     38- ''n'' : is the list of indices of the time axis in the forcing file and readdim2.f90 will step from n-1 to n. 
     39- ''itau'' : is the time stepping of ORCHIDEE and takes 'split' values between n-1 and n. 
    4040 
    41 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. 
     41The 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. 
    4242 
    43 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. 
     43All 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. 
    4444 
    45 The issue becomes more complicated when we consider fluxes which are averaged over an interval. We can only make the assumption that the time corresponding to index n is within the time interval of the average. But we in readim2.f90 we have no way of knowing if it is at the start, end or anywhere else. 
     45The issue becomes more complicated when we consider fluxes which are averaged over an interval. We can only make the assumption that the time corresponding to index ''n'' is within the time interval of the average. But we in readim2.f90 we have no way of knowing if it is at the start, end or anywhere else. 
    4646 
    4747The graphic below explains probably better the above description. 
    … …  
    5050 
    5151 
    52 The figure is especially meant to illustrate that the interpolation for fluxes assumes that the interval of validity of the fluxes at index n is assumed implicitly by readim2.f90 to be between n-1/2 and n+1/2. 
     52The figure is especially meant to illustrate that the interpolation for fluxes assumes that the interval of validity of the fluxes at index ''n'' is assumed implicitly by readim2.f90 to be between ''n-1/2'' and ''n+1/2''. 
    5353 
    5454== Add an explicit time information within the forcing files ==