ECC-1796: Implement stepRange indexing for DestinE ExtremesDT and On-Demand ExtremesDT data #204
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
…ate-dt where step is not used.
…ince in other datasets mars.step is set to stepRange
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.
Development so that stepRange is used to index temporally processed fields rather than endStep. This is an important addition which means that two temporally processed fields over different time ranges can be distinguished and won't overwrite each other when written to the fdb or archived.
ClimateDT uses date and time to index and not step, so we apply this change to all other datasets.
See https://jira.ecmwf.int/browse/ECC-1796