You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To save disk space the last go around of creating surface datasets we decided to deprecate the half degree grid. And we didn't create default 360x720cru surface datasets in our last go around of creating a set of surface datasets. Because, of TRENDY, and desires of mizuRoute and the fact that 360x720cru is on the same grid that our standard GSWP3 forcing is on, we are going to start supporting this as a standard grid. So we'll create surface datasets for its use and make it a standard thing that we create when we create all of the surface datasets.
To start off with we won't create landuse.timeseries files. But, that might be added in when needed later. For the high resolution datasets we should likely split the timeseries files into the segments that will most likely be run. For the lower resolution cases we like to have the future scenario data repeat the historical section (1850-2015) as it gives more flexibility in running cases that run up to the current day.
The text was updated successfully, but these errors were encountered:
To save disk space the last go around of creating surface datasets we decided to deprecate the half degree grid. And we didn't create default 360x720cru surface datasets in our last go around of creating a set of surface datasets. Because, of TRENDY, and desires of mizuRoute and the fact that 360x720cru is on the same grid that our standard GSWP3 forcing is on, we are going to start supporting this as a standard grid. So we'll create surface datasets for its use and make it a standard thing that we create when we create all of the surface datasets.
To start off with we won't create landuse.timeseries files. But, that might be added in when needed later. For the high resolution datasets we should likely split the timeseries files into the segments that will most likely be run. For the lower resolution cases we like to have the future scenario data repeat the historical section (1850-2015) as it gives more flexibility in running cases that run up to the current day.
The text was updated successfully, but these errors were encountered: