Datasets #13
Closed
Datasets #13
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
Add CONTRIBUTING.rst file in root dir
Documentation updates
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.
Wanted to start discussion on this first draft of Dataset class and Pipeline class functionality to .run(Dataset).
This approach introduces a filesystem described at the top of Dataset.
Changes are tested on a small folder of slides and it runs. (can create a dataset and run pipeline)
Some things aren't finished:
Do we want tiles written individually in a folder for each slide, or do we want to package the tiles for each slide (hdf5?)?
Pipeline.extract_tiles has awkward property that it takes dataset so it can add paths to tiles.
I will add parallelization to pipeline for Dataset objects.