-
Notifications
You must be signed in to change notification settings - Fork 247
[WIP] Add new torchvision models #219
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
Conversation
✔️ Deploy Preview for pytorch-hub-preview ready! 🔨 Explore the source changes: 0f739f5 🔍 Inspect the deploy log: https://app.netlify.com/sites/pytorch-hub-preview/deploys/6133c0f1416fd30007c6179e 😎 Browse the preview: https://deploy-preview-219--pytorch-hub-preview.netlify.app |
The old pages are still persisting along with the new pages. But I don't rename the files they would convey a wrong meaning. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the PR @oke-aditya , this is very useful
I took a brief look even though this is still WIP, LMK when this is ready for a full round. Considering the big amount of changes I would suggest to include the rest of the models in other PRs, too keep reviews manageable.
Also, unfortunately our CI is completely toasted at the moment: https://app.circleci.com/pipelines/github/pytorch/hub/1244/workflows/a94283ed-e5cc-4c8c-b4cf-9ba78a03900c/jobs/1677 because of all those rate API limit issues. Hopefully it should be fixed in a near future, but sadly it means we'll have to wait until the CI is back again to merge this PR (but we can still do most of the review in the mean time)
Something I found out in log
I think this should be addressed by pytorch.github.io team. |
Thanks for raising this, we'll notify the relevant team |
Hmm the open in Colab will not work as of now. I think it would need the notebook in pytorch.gihtub.io repo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would love your thoughts @NicolasHug and @datumbox
I need to go through the blog and papers to update descriptions of these models.
|
||
Here's a small snippet that plots the predictions, with each color being assigned to each class (see the visualized image on the left). | ||
|
||
```python |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if it would be good to use torchvision utils.
Since they are from v0.10+ it might not be backward compatible.
Let me know.
@malfet @seemethere , @jspisak suggested that one of you guys might be able to help with this :) ? |
I will complete the PR this week mostly. Sorry for the delay. Edit: |
@oke-aditya it seems to me you missed* one model. * Or I sneakily added the new EfficientNet to your list. 😄 |
So the only thing left now is to add descriptions about the models.
I think I can finish this hopefully over the weekend. |
|
||
```python | ||
import torch | ||
model = torch.hub.load('pytorch/vision:v0.11.0', 'efficientnet_b0', pretrained=True) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that it would be wrong to mention pytorch/vision:v0.10.0
as the model was not added till then.
It will be available in the coming 0.11 release.
Should we merge efficientnet now or after the 0.11 release?
I'm happy either ways, we can keep a separate PR open and merge after the release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah that's a good point... Good call. Do you want to remove this from the PR and send the addition on a separate? We could leave it unmerged until the release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool! I will remove the efficientnet files from current PR and keep them on separate one.
As you suggested, we can merge it after release 👍
@oke-aditya thanks for your work on this, in order to keep the reviewing manageable would you mind creating one PR per model? |
Ok sure no problem. I will close this PR and re-open new ones which add models one at a time. |
pytorch/vision#4289
Adds the following models.
I modified the DeepLab and FCN files inplace to avoid duplicating. It needed a small rename in the file.
I have added a couple of images denoting architecture of mnasnet and mobilenetv3.
Let me know if those images are fine.
The model description is pending for lr_aspp, mnasnet and MobileNetV3.
But a small review at this point would be great.
cc @datumbox @NicolasHug