Open akubaryk opened 4 years ago
From some email exchanges:
I see that, when coupled, IPE still initializes the IPE_Time class using the initial timestamp included in IPE.inp.
The IPE time class contains a whole bunch of 'home grown' time routines
- one of these is a leap year function which is probably the problem here.
YearMonthDay [...] (365*year + year/4 - year/100 + year/400)
Commit 1e6f917 solves this issue when IPE is running coupled. IPE's internal clock is still faulty and needs to be fixed.
@gmillward did we actually get the problem fixed?
For example, when initializing the coupled model from 2015030100 and IPEFREQ=3600, IPE's first output will be timestamped 201502290100. There's likely an issue in the time handling, IPE_Time_Class.