-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate axes types v0.4 #124
Merged
Merged
Changes from 8 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
9250136
Add new current version 0.4
will-moore 6557b26
writer validates axes for 0.4 version
will-moore 19a320c
reader handles axes as None, List of str or List of dict
will-moore a2b3b3e
Add tests
will-moore 02342b6
Fix logging of axes names
will-moore 939295c
Don't reassign axes - fix mypy
will-moore 789b95b
Check for axes is None - fix mypy
will-moore 4097ece
Fix logging of axes names for v0.4 and v0.3
will-moore bd16dfd
Use validate_axes() in reader.py
will-moore 9f75ae3
Move axes logic to new Axes class
will-moore 18608d9
Fix various points from Seb
will-moore a580788
Merge remote-tracking branch 'origin/master' into validate_axes_types…
will-moore 7147bbd
Rename get_axes() -> to_list()
will-moore 8e37f31
Rename writer.validate_axes() to _get_valid_axes()
will-moore 3037b33
Axes() constructor also calls self.validate()
will-moore 5607786
Handle transformations in reader and writer. Add test
will-moore d9a44f7
reader node.metadata['axes'] in latest format
will-moore File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the main implication of not setting a default value here?
For 0.1/0.2 data, this means, the
node.metadata["axes"]
might beNone
as opposed to["t", "c", "z", "y", "x"]
previously i.e. we are preserving the value stored in the metadata? Is there an impact on clients relying onnode.metadata["axes"]
?