-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Add visibility parameter to draw_keypoints() #8225
Conversation
Added visibility attribute to draw_keypoints Added example in gallery Added tests
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/8225
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (27 Unrelated Failures)As of commit 39d23b7 with merge base 36d0e3e (): FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Added missing comma
I diddn't run ufmt and flake on the gallery and tests, my bad. Now everything worked locally. I'm still wondering about how to display the new prediction matrix. "000.000" looks nice but is not good practice. And if I want the values to align, I can't use spaces. |
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.
Thanks a ton @bmmtstb , I made a few comments but this looks great already!
Co-authored-by: Nicolas Hug <contact@nicolas-hug.com>
Co-authored-by: Nicolas Hug <contact@nicolas-hug.com>
Co-authored-by: Nicolas Hug <contact@nicolas-hug.com>
Added test that compares skeleton creation with visibility Added test that calls draw_keypoints with visibility of None Used link draw_keypoints_with_visibility moved visibility to the back of draw_keypoints call removed inplace modification of visibility variable removed redundant comments
@NicolasHug I implemented most of your requests. Additionally, I could add a test against a dummy image as proposed by you. Sadly I needed to create a new image and couldn't reuse the existing one, see comments above. |
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.
Thank you so much @bmmtstb , some last comments below but this looks great. I can take care of addressing those comments if you prefer, LMK
This reverts commit da5fc4a.
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.
Thank you so much @bmmtstb !
Reviewed By: vmoens Differential Revision: D55062800 fbshipit-source-id: fc29a5ea8c5e40b7862a5522bffd73de4c44e080 Co-authored-by: Nicolas Hug <contact@nicolas-hug.com> Co-authored-by: Nicolas Hug <nh.nicolas.hug@gmail.com>
Added visibility attribute to draw_keypoints
Added another section to the draw_keypoints example in the gallery
Added tests in test_utils
I'm not entirely sure how to full / properly test the skipped connections, but in visual inspection everything seems fine.
Waiting for your comments @NicolasHug
A few things to note:
num_instances
andN
gets used to describe the same thing. Possibly double check that.~torch.Tensor
as type hint for the visibility, not~torch.BoolTensor
.