Changes between Version 76 and Version 77 of Documentation/Forcings

Timestamp:

2018-01-31T11:31:08+01:00 (6 years ago)

Author:

aducharne

Comment:

--

Documentation/Forcings

@@ -51 +51 @@
 
 (b) '''Two versions of the driver are available''' to do do both the reading and the inter/extrapolation of the forcing datasets. They differ in the way they interpret the time at which the diffrent variables are read in the forcing dataset (further called the timestamp, while the interval refers to the period between two succesive timestamps):
-* '''the old driver (src_driver/dim2driver)''', which assumes that scalar variables (Tair,Qair,Psurf) are instantaneous values at the timestamp, while flux variables (Rainf,Snowf, SWdown, LWdown) are mean values over the interval ending at the timestamp. The old driver also needs a forcing that has its first record at 0 UTC to work correctly.
+* '''the old driver (src_driver/dim2driver)''', which assumes that scalar variables (Tair,Qair,Psurf) are instantaneous values at the timestamp, while flux variables (Rainf,Snowf, SWdown, LWdown) are mean values over the interval ending at the timestamp. 
 * '''the new driver (src_driver/orchideedriver.f90) is more flexible''' and can normally deal with any temporal structure of the forcing datasets, provided the required attributes are inserted in the forcing files. This document [attachment:Description_Forcing_Files.pdf] provides detail of how forcing files need to be prepared. It addresses in particular the issues one may face when the fluxes are averaged and scalar variables instantaneous. The driver needs to take this into account else the diurnal cycle needs to be misplaced. Some data providers have different convention for representing averaged fluxes and this type of details matter.