Closed stchepounoff closed 5 years ago
Yes, the code is quite dirty, and wrong, around that place. It will be cleaned for next version
Before it is released, you can circumvent the problem by simplifying your period from '1996010100-1999123123' to '1996-1999', which represents exactly the same thing for CliMAF (see the two last examples in init_period doc)
Fixed with commit 0bb5a6e
trying to declare a climaf dataset with period 1996010100-1999123123 => File "/cnrm/est/COMMON/climaf/current/climaf/period.py", line 242, in init_period raise Climaf_Period_Error("period end string %s is not a date"%end) climaf.period.Climaf_Period_Error: 'period end string 1999123123 is not a date'
The problem is the treatment beginning on line 231 of module period.py.
Solution may be :+1:
if (ehour > 23) : ehour=0 months_days = [31,28,31,30,31,30,31,31,30,31,30,31]