-
Notifications
You must be signed in to change notification settings - Fork 7.1k
Add ssTEM dataset #900
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
Add ssTEM dataset #900
Conversation
I'm not sure about this. IMO we should not have a dataset (or in this case a split of the dataset) without labels. @fmassa ? |
Codecov Report
@@ Coverage Diff @@
## master #900 +/- ##
==========================================
- Coverage 57.9% 57.45% -0.45%
==========================================
Files 46 47 +1
Lines 3696 3756 +60
Branches 561 572 +11
==========================================
+ Hits 2140 2158 +18
- Misses 1429 1473 +44
+ Partials 127 125 -2
Continue to review full report at Codecov.
|
@fmassa What's the status of this PR? Is this something that is still wanted, or should I close it? |
It seems like this PR has been abandoned by upstream, so I'm going to close it. Feel free to reopen or steal these commits to make a new PR. |
This PR adds a dataset for ISBI Challenge: Segmentation of neuronal structures in EM stacks, which involves imagery from an ssTEM microscope.
Questions:
This dataset requiresskimage
to load, as it includes multi-channel TIF images that PIL does not support. How should we handle this? Should I make theskimage
import lazy so that it isn't required to importtorchvision
?This is a segmentation dataset. As such, most transforms like RandomHorizontalFlip and RandomAffine must be applied to both img and target. Is their any precedence for how to handle this? Or should I have a separatetransform
andtarget_transform
like other datasets?