Adding support for keypoint names/labels other than the ones used in the COCO dataset #139
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
…ead of hard-coded ones.
…o avoid duplicating them.
|
|
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.
Hi,
This is the PR corresponding to the issue with the same name here.
This PR aims to remove the hard-coded COCO category names, and to replace them by the ones present in the dataset.
This allows to use the tool for datasets where the keypoints are not defined for humanoid shapes.
The PR also adds the keypoints names and skeleton to the first category of the COCO json file. This does not guarantee that they are attached to the correct category, but this will be fine if only one type of object is present (and it is likely better than not having the information at all).