draw_keypoints() float support
Follow-up PR: #8150
Hey there!
I've added functionality to the draw_keypoints() method, allowing it to handle both uint8 and float32 image types. I welcome any feedback you may have on these changes.
Thank you!
:link: Helpful Links
:test_tube: See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/8276
- :page_facing_up: Preview Python docs built from this PR
Note: Links to docs will display an error until the docs builds have been completed.
:x: 3 New Failures, 4 Unrelated Failures
As of commit c9fd6ca77c9e1c30299c19c325c69081385c50fb with merge base c8c3839cb9b0fc52885cafa431460f686c46f5ae ():
NEW FAILURES - The following jobs have failed:
-
Build Aarch64 Linux Wheels / pytorch/vision / upload / wheel-py3_8-cpu-aarch64 (gh)
Unable to find any artifacts for the associated workflow -
Build Linux Wheels / pytorch/vision / upload / manywheel-py3_8-cuda11_8 (gh)
Unable to find an artifact with the name: pytorch_vision__3.8_cu118_x86_64 -
Build M1 Wheels / pytorch/vision / upload / wheel-py3_8-cpu (gh)
Unable to find any artifacts for the associated workflow
FLAKY - The following job failed but was likely due to flakiness present on trunk:
-
Tests / unittests-linux (3.9, linux.12xlarge, cpu) / linux-job (gh)
The process '/usr/bin/git' failed with exit code 128
BROKEN TRUNK - The following jobs failed but was present on the merge base:
👉 Rebase onto the `viable/strict` branch to avoid these failures
-
Build Linux Wheels / pytorch/vision / upload / manywheel-py3_8-cpu (gh)
Unable to find an artifact with the name: pytorch_vision__3.8_cpu_x86_64 -
Build Linux Wheels / pytorch/vision / upload / manywheel-py3_8-cuda12_1 (gh)
Unable to find an artifact with the name: pytorch_vision__3.8_cu121_x86_64 -
Build Linux Wheels / pytorch/vision / upload / manywheel-py3_8-rocm5_7 (gh)
Unable to find an artifact with the name: pytorch_vision__3.8_rocm5.7_x86_64
This comment was automatically generated by Dr. CI and updates every 15 minutes.
Hey @NicolasHug,
Thank you for pointing out my mistakes. While it might be second nature for you to find these bugs, I am still in the learning process. I apologize for making you go through my code once again.
Thanks again.
No problem at all @GsnMithra thank you for the PR