Create a utility class with dask-cuda that mimics Pytorch's DataLoader #120
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
|
cc @gigony (for awareness) |
gigony
added
feature request
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.
This is a draft PR to resolve the feature request #99.
Two types of PyTorch Dataset classes are provided here - one Iterable-style Dataset and one Map-style Dataset. Both of these utility classes are empowered by CuPy-backed Dask Arrays - which allow for zero-copy data transfer to PyTorch. Dask is utilized to allow for scheduling of CuPy array transformations (such as CuCIM operations) before delivering the data to PyTorch's Dataloader.
First, please see this gist example of the Map-style Dataset in action.
Next, please see this gist example of the Iterable-style Dataset in action.