Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Thanks for @sacmehta 's talent work,
I have made one change for easy using of this project,
main.py :
1. add ignored_Id argument to notice which ID (in the label file) should be ignored.
2. the default value of ignored_Id is 255 (for cityscapse trainID of )
3. using torch.nn.crossEntryLoss to replace the user defined crossEntryLoss entity, and pass
ignored_Id to ignore_Index parameter of torch.nn.crossEntryLoss.
loaddata.py
4. when check the max_value in the label file, compare it with ignored_Id first, then print some
information to notice the ignored_Id in the label file has been ignored
these changes have been verified in ubuntu 16.04 , cuda 9.0 cudnn 7.0, pytorch 1.0.0 post2,
Thanks for your time and looking for your reply.