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

pre-millennial time-series files no longer need to be broken up into smaller segments... #755

Closed
ekluzek opened this issue Jun 26, 2019 · 1 comment
Assignees
Labels
enhancement new capability or improved behavior of existing capability
Milestone

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Jun 26, 2019

Previously we broke up the pre-millennial time series files into smaller segments of 250 years. We are now using 64-bit offset NetCDF for the time-series files and so we don't have the previous limit on file size. So I don't think there is a reason to break it up this way anymore. The resulting file will be about 100GB, but that isn't as big of a problem as it used to be, and it's probably easier to manage one big file rather than four files, as well as requiring simulations to be broken up into four segments. Since, it only reads each time segment into memory while running the model, I don't see a reason that we have to break it up anymore now that we can read larger files.

@dlawrenncar @lawrencepj1

@ekluzek ekluzek added enhancement new capability or improved behavior of existing capability priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations branch tag: release Changes go on release branch as well as master labels Jun 26, 2019
@ekluzek ekluzek added this to the cesm2.1.2 milestone Jun 26, 2019
@ekluzek ekluzek self-assigned this Jun 26, 2019
@ekluzek ekluzek added next this should get some attention in the next week or two. Normally each Thursday SE meeting. and removed priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations labels Jul 15, 2019
@billsacks billsacks removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Jul 29, 2019
@ekluzek
Copy link
Collaborator Author

ekluzek commented Oct 7, 2019

The files I've created are a single file from 850-1850. This was brought into release-clm5.0.27.

@ekluzek ekluzek removed the branch tag: release Changes go on release branch as well as master label Oct 7, 2019
@ekluzek ekluzek closed this as completed May 22, 2020
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
None yet
Development

No branches or pull requests

2 participants