Changes between Version 28 and Version 29 of Branches/Driver_Improvements
- Timestamp:
- 2016-05-27T18:23:43+02:00 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Branches/Driver_Improvements
v28 v29 17 17 Now we need to remember where we are in the code, and what we need the forcing for. When we read itau_n, with values corresponding to t0+dt, sechiba hasn't yet run between t0 and t0+dt. It has run (or been initialized) up to t0, with forcing controlled by the forcing records itau_nm1 and before. '''So when we read the record itau_n corresponding to the time stamp t0+dt, we know the state of sechiba at t0, the forcing values at t0 (from itau_nm1), and we want to correctly define the forcing variables over each dt' between t0 and t0+dt (dt=split*dt').''' 18 18 19 For me, these are general principles which need to be true whichever the forcing if we decide to read together all the variables that have the same time stamp. The fact that fluxes are averages over a period of length dt after or before the time stamp can be dealt with in the above general framework , at the initialisation stage(but the latter is an opinion).19 For me, these are general principles which need to be true whichever the forcing if we decide to read together all the variables that have the same time stamp. The fact that fluxes are averages over a period of length dt after or before the time stamp can be dealt with in the above general framework (but the latter is an opinion). 20 20 21 21