-
Notifications
You must be signed in to change notification settings - Fork 463
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
是否可以支持export yolo pose format? #103
Comments
Hi, @ckcraig01 : Thank you for your support! |
Thank you for your promptly feedback. we could find yolov8-pose only by building from source. However, from the results of its inference, it is still lacking a group_id, which means it can't build associations. The output results can be imagined as if we used a separate person detector (e.g., YoloV7) + a separate 5-keypoint regressor (e.g., RSN-18), which would yield the same effect. However, this obviously doesn't effectively associate the landmark features with the person. Thanks again. |
Hi, @ckcraig01, thank you for your kindly feedback and valuable input. I'm pleased to inform you that the As for the compiled executable version would be provided as soon as possible. Your suggestions are greatly appreciated, and I'm committed to making the tool even more effective for associating landmark features with individuals. If you have any further questions or need assistance, please don't hesitate to reach out. Best regards, |
Thanks for your feedback. Best wishes for a thoroughly success |
感謝精美的作品, 目前看到有: yolov6-lite face的model
希望能支持輸出格式, 包含bbox + kpts.
https://github.com/ultralytics/ultralytics/blob/main/docs/datasets/pose/index.md
...
In this format, is the index of the class for the object, are coordinates of bounding box, and
... are the pixel coordinates of the keypoints. The coordinates are separated by spaces.
也許需要定義對應的yaml, 如文中:
(當然instance seg. -> bbox + instance seg. 也希望能支持)
https://github.com/ultralytics/ultralytics/blob/main/docs/datasets/segment/index.md
能適配yolov5/v6/v7/v8的使用, 我認為會非常有幫助, 謝謝!
The text was updated successfully, but these errors were encountered: