Update VGG error rates
#319
Open
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
updates according to numbers from: https://pytorch.org/vision/main/models.html#table-of-all-available-classification-weights `torchvision` documentation version: `main (0.15.0a0+23c2e5f )`
✅ Deploy Preview for pytorch-hub-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
Updated error according to numbers from: https://pytorch.org/vision/main/models.html#table-of-all-available-classification-weights.
torchvisiondocumentation version:main (0.15.0a0+23c2e5f ).For consistency with the numbers from
torchvision, I have not rounded the numbers to 2 decimal places but to 3 where necessary.Closes #313.
As you say @NicolasHug in #318, I too think it might be for the best to refer to
torchvision's documentation for accuracy numbers. Doing it like this is not ideal. Especially so, since this has a table of error rates andtorchvisionaccuracies.