Add reusable subsetting API #55
Merged
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.
#20
#16
This brings a new API to create selector objects to subset on demand. These objects are pickleable so they can be used more efficiently than doing the subset again.
This is super useful, because a data provider or researcher can now predefine their subsets and deliver them from the cloud performantly wihtout having to export entire datasets or compute nodes at request time
See the stofs_3d notebook for an example where an STOFS_3D dataset is read in, subset, the selector is saved via
pickleand then loaded back usingpickleand used to subset a new dataset.