Shawn P. Serbin

@ankurdesai issue is that 0 and 365 get parsed as the same date: https://github.com/PecanProject/pecan/issues/2094#issuecomment-418801635

What we need is a standard way we define time in netCDF, which includes days since, calendar type, and how the time values are specified such that we avoid the...

It would seem that we actually want to first determine the posix date and then generate the DOY tvals from this.... and also that we need to start with 0,...

...or perhaps we start to use time bounds, e.g. ``` double time(time) ; time:units = "days since 1850-01-01 00:00:00" ; time:calendar = "noleap" ; time:axis = "T" ; time:long_name =...

@mdietze take a look at https://github.com/PecanProject/pecan/pull/2095 Probably still some cleanup but I have tested on modex (command and via web) and it doesnt break PEcAn but does provide the additional...

For example, global CLMCN output ``` netcdf rsds_Amon_CLM40cn_historical_r1i1p1_185001-201012 { dimensions: time = UNLIMITED ; // (1932 currently) lat = 192 ; lon = 288 ; levgrnd = 15 ; levlak...

and here is CLM-FATES output ``` float time(time) ; time:long_name = "time" ; time:units = "days since 1900-01-01 00:00:00" ; time:calendar = "noleap" ; time:bounds = "time_bounds" ; int mcdate(time)...

Updates to fates to reflect new ACME restructuring: Update create ref case file (done) Update clm and fates param files in fates/inst/ (in process) - These are the new files...

Following FATES refactoring we still need the following three PRs: 1) Enable cloning of ref-case rather than building new for each ensemble member (priority 1) 2) Enable running with PEcAn...

Update TODO: update code to read param files (CLM and FATES) out of the refcase directory, not the PEcAn package TODO: update to allow it to pick between CLM4.5 and...