Changes between Version 46 and Version 47 of Branches/Driver_Improvements

Timestamp:

2016-06-09T14:50:38+02:00 (8 years ago)

Author:

nvuilsce

Comment:

--

Branches/Driver_Improvements

@@ -15 +15 @@
 Where dt is the time step of the forcing file. 
 
->'''AD (26/5/16)''': Note that, in the above case, the time at which we read the forcing is t0+dt. Let's introduce an index itau of the forcing records: itau=1 is the first record in the nc file for all variables, etc.
+>'''AD (26/5/16)''': Note that, in the above case, the time at which we read the forcing is t0+dt. 
+>> NVui: To my opinion, the time at which we read the forcing is t0, not t0+dt because the instantaneous value at t0+dt is needed to interpolate the field from the t0+dt' time step and the mean value between t0 and t0+dt is needed from the t0 time step. 
+>> 
+>> I would like also to remind that in the current driver, the information stored in the time variable (or timestp variable) is not used for defining the time stamp. Consequently, what is written here about the timestamp and the time at which the data is relevant (instanteneous, +dt, ...) is only implicit here. The time or timestp variable in the Netcdf file is only used for defining the timestep (dt) of the forcing. 
+    
+>Let's introduce an index itau of the forcing records: itau=1 is the first record in the nc file for all variables, etc.
 >
 >Imagine we are currently reading the record itau_n, coming juste after the record itau_nm1. These are the notation of dim2driver/read2dim, and we have itau_n=itau_nm1+1. The "time_stamps" corresponding to these two records are separated by dt (the dt between two records, and not dt_sechiba=dt': dt=split*dt'). To make the link with the above notations of time, the time stamp of the record itau_n is t0+dt, and the one of of itau_nm1 is t0.