Flexible splits #125
Merged
Flexible splits #125
Conversation
This file contains 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
Let the user specify along which dimensions to split. To avoid mismatches between the split dimensions and the output file pattern, the split dimensions are extracted directly from the output formatting.
alxmrs
reviewed
Mar 31, 2022
alxmrs
reviewed
Mar 31, 2022
…FileInfo, removed redundant method in FileSplitter.
…ools into flexible_splits
alxmrs
reviewed
Apr 4, 2022
alxmrs
reviewed
Apr 4, 2022
alxmrs
reviewed
Apr 8, 2022
alxmrs
reviewed
Apr 8, 2022
alxmrs
reviewed
Apr 8, 2022
alxmrs
reviewed
Apr 8, 2022
alxmrs
reviewed
Apr 8, 2022
alxmrs
reviewed
Apr 8, 2022
alxmrs
reviewed
Apr 8, 2022
alxmrs
reviewed
Apr 8, 2022
alxmrs
reviewed
Apr 11, 2022
alxmrs
reviewed
Apr 11, 2022
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.
Allow more flexible splitting.
Dimensions to split along are specified using output formatting to avoid mismatch between formatting and splitting.
Possible splits for GRIB files are all metadata fields, like shortName, typeOfLevel, date, time, step, forecastTime, etc.
Possible splits for NetCDF files are 'level', 'time', 'variable'. If the specified dimension (time, level) is not in the file, and exception will the thrown.
Output formatting can be given using an output template that contains formatting marks, or an output directory with an additional formatting string. If an output directory is specified without formatting, file type-specific defaults are used.