Istem Fer

correct me if I'm wrong, but the only adjustment for timezone issues is in met2model.ED. And it just adds buffer in front of the time-series which results in losing data...

thanks @mccabete hmm where to address this then I feel like it would be the easiest to handle it in the post processing, rather than adding buffer to the met...

different flavors of what happens to the model-data comparison in the 2006 part of one of my 2005/06/01 - 2006/12/31 runs (red : data, blue : model output read by...

I tried giving different start/end dates, it complained that there is no 2007JAN.h5 but I guess this is solvable by changing a flag in ED2IN (so that it recycles the...

back to this. @mdietze what do you think? So, there was an issue due to the hardcoded `-21600.0d0`s in ED2's timestamps (also see issue [#231](https://github.com/EDmodel/ED2/issues/231)) once we get rid of...

after today's meeting, adjusting for timezone in model2netcdf.ED2 might not be the way to go..rather, load_data will bring everything to UTC? just tagging @bcow here

I think that's a pretty old bit of code, looks like noone has used ED through pecan in the Eastern Hemisphere? My understanding was that in pecan we decided to...

we access standard netcdf file variables by name (the ones created by model2netcdf) if needed, iirc we don't assume a particular order anywhere after this. So, unless ED code changes...

I think we still have `s` and numbers in there. I'll defer to other people who are currently actively working with ED on whether to close or implement this

I think it works now, thanks for the changes whomever made it. But I want to point out that some of the links that are linked via BETY [paper appendix](https://onlinelibrary.wiley.com/action/downloadSupplement?doi=10.1111%2Fgcbb.12420&file=gcbb12420-sup-0003-AppendixS3.pdf)...