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

fixed typo in docs #1851

Merged
merged 1 commit into from Feb 10, 2020
Merged

fixed typo in docs #1851

merged 1 commit into from Feb 10, 2020

Conversation

akshaykulkarni07
Copy link
Contributor

input to parameter mode can be 'fine' or 'coarse'. The code internally converts the mode = 'fine' input to 'gtFine' (same for coarse input and gtCoarse), but the docs mention that input to mode should be 'gtFine' or 'gtCoarse' inconsistently.

input to parameter mode can be 'fine' or 'coarse'. The code internally converts the mode = 'fine' input to 'gtFine' (same for coarse input and gtCoarse), but the docs mention that input to mode should be 'gtFine' or 'gtCoarse' inconsistently.
Copy link
Member

@fmassa fmassa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@fmassa fmassa merged commit 6995a79 into pytorch:master Feb 10, 2020
fmassa pushed a commit to fmassa/vision-1 that referenced this pull request Jul 8, 2020
input to parameter mode can be 'fine' or 'coarse'. The code internally converts the mode = 'fine' input to 'gtFine' (same for coarse input and gtCoarse), but the docs mention that input to mode should be 'gtFine' or 'gtCoarse' inconsistently.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants