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.
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
Properly handle maskrcnn and keypoints w.r.t. V2 in detection references #7742
Properly handle maskrcnn and keypoints w.r.t. V2 in detection references #7742
Changes from all commits
28293dc
03767e8
dc584dc
c8a2cb0
d076b4c
2f3f15c
044336a
511f323
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Maybe we should remove the
get_masks
parameter ofget_coco()
and just make it part of themode
parameter, i.e. allow "instances", "instances_masks", and "keypoints".ooooor just completely change the parametrization of
get_coco()
to something more friendly.In addition to that, the way we magically specify keypoints or masks (through dataset name or through model name) is pretty terrible right now.
I feel like we should address that for good, but I'd prefer doing it in another PR
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.
Yes, I agree that it would be better that
args.dataset
could parametrize data type instead of the model name.args.dataset
can be "coco, "coco_kp" and "coco_masks", for example.