Skip to content
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

Semantic segmentation model #259

Merged
merged 76 commits into from
Oct 21, 2020
Merged

Semantic segmentation model #259

merged 76 commits into from
Oct 21, 2020

Conversation

annikabrundyn
Copy link
Contributor

@annikabrundyn annikabrundyn commented Oct 2, 2020

Model for semantic segmentation task that uses Unet architecture and Kitti datamodule by default.
I've added simple tests for Unet, Kitti DM and SemSegment model + updated docs.

Three things I was unsure of:

  1. To use Kitti dataset you have to manually download it and provide the local directory to the data module - how can I add checks or tests to ensure that someone has downloaded the kitti dataset?

  2. Ideally the SemSegment model should be generalizable - this specific example uses the UNet architecture but you should be able to override this with your own architecture. Any suggestions or examples for how to add this flexibility to the model?

  3. Where should these models be housed? I've put both UNet and SemSegment under Vision since this seemed the most general. I've implemented UNet as just an architecture to plug into other models like SemSegment. Let me know if you think they should be moved!

Also, I wasn't able to train the model on Kitti because of issues with uploading the data to a cluster. I'm thinking I'll train on PascalVOCSegmentation from torchvision instead :)

@mergify
Copy link
Contributor

mergify bot commented Oct 7, 2020

This pull request is now in conflict... :(

@mergify
Copy link
Contributor

mergify bot commented Oct 13, 2020

This pull request is now in conflict... :(

@mergify
Copy link
Contributor

mergify bot commented Oct 14, 2020

This pull request is now in conflict... :(

@mergify
Copy link
Contributor

mergify bot commented Oct 15, 2020

This pull request is now in conflict... :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants