Changes between Version 6 and Version 7 of Branches/Driver_Improvements

Timestamp:

2012-10-25T16:40:06+02:00 (10 years ago)

Author:

nvuilsce

Comment:

--

Branches/Driver_Improvements

@@ -8 +8 @@
 All time information are defined on UTC time.
 The fields read at a certain time step t in the NetCDF file correspond to:
- * the instantaneous value at t of scalar variables :  Temperature, Wind Speed, Air Pressure and Specific Humidity. 
- * the mean value between t and t+1 (or t-1 and t) for fluxes : Long and Short Wave incoming Radiation and the Precipitation. 
+ * the instantaneous value at t+1 of scalar variables :  Temperature, Wind Speed, Air Pressure and Specific Humidity. 
+ * the mean value between t and t+1 for fluxes : Long and Short Wave incoming Radiation and the Precipitation. 
 The time interval represented by each variable needs to be documented in the netCDF file (see below).
 
@@ -23 +23 @@
 We suggest to add a time_bounds attribute to the time variables stored in the Netcdf forcing file according to the CM convention : http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html
 
-Each file will contain at least 2 time axes, one for the scalar variables and one for the flux variables. Each of the time axes will have its "time_bounds" variable in order to describe the interval each value describes.
+Each file will contain at least 2 time axes, one for the scalar variables and one for the flux variables. Each of the time axes will have its "time_bounds" variable in order to describe the interval each value describes. A time_op attribute (average, point) for each variable could be also added. The time specification of a forcing file (based on time_bounds and time_op attributes) should be read by the driver, in order to check for consistency.
 
 Questions that remain: