Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 360x720cru surface datasets and maintain as a regular grid #1483

Closed
ekluzek opened this issue Sep 9, 2021 · 1 comment · Fixed by #2372
Closed

Add 360x720cru surface datasets and maintain as a regular grid #1483

ekluzek opened this issue Sep 9, 2021 · 1 comment · Fixed by #2372
Assignees
Labels
enhancement new capability or improved behavior of existing capability
Milestone

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Sep 9, 2021

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.

@ekluzek ekluzek added the enhancement new capability or improved behavior of existing capability label Sep 9, 2021
@ekluzek ekluzek self-assigned this Sep 9, 2021
@ekluzek ekluzek mentioned this issue Oct 7, 2021
@ekluzek
Copy link
Collaborator Author

ekluzek commented Apr 10, 2024

This will be fixed in ctsm5.2 #2372

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant