Path naming fixes #102
Merged
Path naming fixes #102
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
|
👍 |
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.
@tcchiao @norlandrhagen @jhamman
Two fixes here in response to the most critical aspects of Issue #98 (not the optional naming convention switches):
grid_specback into the paths - without it we will read the same obs dataset for every GCM which wouldn't match in gridchunking_approachmethod back in. This ensures that the coarsened obs used at any given point is chunked in the right way. This fix will make thefull_timechunked dataset to be used for model training (it isn't being made before this PR).