New chunking strategy to support CMIP7 repacking requirements#894
Merged
New chunking strategy to support CMIP7 repacking requirements#894
Conversation
…is if it is defined. Otherwise, use the default size defined by CMOR_DEFAULT_TIME_CHUNK_SIZE
…unk size stays under a maximum size
Closed
durack1
approved these changes
Jan 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #880
This changes how CMOR performs chunking of the variable data along time and spatial dimensions.
Key changes
These changes do not enforce the "consolidated metadata" repacking requirement where the chunking index b-tree must be stored contiguously at the beginning of the file. However, it should reduce the work needed to be done by cmip7repack by avoiding rechunking the data variable.