Shawn P. Serbin
so it seems we need to be ending in the 364. part for non leap and 365. for leap, for example ``` >>> from netCDF4 import num2date,date2num >>> print num2date(365.,"days...
For ED2 I propose we change to: ``` > days head(days) [1] 0.00000000 0.02083333 0.04166666 0.06249999 0.08333332 0.10416665 > tail(days) [1] 363.8958 363.9166 363.9374 363.9583 363.9791 363.9999 ``` and ```...
@istfer what version of sipnet are you using that gives you day as 1? I was running r136 or whatever NOT "unk" but yeah that looks like a version issue!...
@istfer OK so narrowing down, here is my input sipnet.clim file ``` 0 2000 0 0 0.04166667 -0.433 0.376 0.000 0.000 100.433 136.257 491.841 3.572 0.291 0 2000 0 1...
Strangely it looks like my runs did not have leap met ``` 0 2004 363 23 0.04166667 -8.001 1.312 0.000 0.000 2.650 339.257 332.666 1.706 0.308 0 2004 364 0...
@istfer did you mean starts with 1 and ends with 365?
@istfer what if we implement something like: ``` if (tail(unique(sipnet.output$day), n=1)==365) { tvals
arrggh that wont work if there is a leap year.
is this harder than it should be because we are inconsistent with how met days are specified to SIPNET? That is sometimes met has a 0 start and sometimes its...
@mdietze I dont think its a version issue, at least for SIPNET, it looks more like an issue of how the met drivers are specified.