fix: account for LeadTimeHour in subset of NORA3 data and also extend reach of metadata for NROA3 to 1958#40
Merged
ErikKusch merged 1 commit intoApr 7, 2026
Conversation
… reach of metadata for NROA3 to 1958
Collaborator
Author
|
Discarding this as the current implementation would lead to issues at year-breaks. Better logic needs to be in place to handle leadtimeHour adjustment across year boundaries. |
Collaborator
Author
|
Nevermind. This did work correctly first try. Typical case of overthinking on closing this. |
ErikKusch
deleted the
39-access_nora3-time-axis-subsetting-fails-for-lead-times-6-9-of-the-final-run
branch
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
1 participant
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.
Fix to respond to #39