Added 3hr versions of some variables#104
Merged
larsbuntemeyer merged 1 commit intomainfrom Apr 10, 2026
Merged
Conversation
larsbuntemeyer
approved these changes
Apr 10, 2026
Contributor
|
Let's see what happens in the CI. I might have to add the new 3hr table initially. data request tools should be able to handle it... |
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
2 participants
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.
This adds some variables at a 3hr frequency in the
datasets.csv, it doesn't affect any actual data requests.The subset of variables added here is the minimal set so that Ouranos' QA passes. I'd be happy to add more if needed.
I assumed a 3hr version of a variable would have the same attributes as the 1hr version. More specifically, if the 1hr has cell methods like "time: point", the 3hr has the same.
Fixes #102.