-
Notifications
You must be signed in to change notification settings - Fork 104
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
Question :Performance against other 2D detectors (openpose) #6
Comments
One thing I notice is that this implementation of hrnet applies the model to the cropped portion of the person returned from yolo whereas, from what I can tell, the model in the original paper is applied to the entire image. Losing the background context when predicting may affect the performance. |
@bpeck81 thanks for the info , actually when i tried to disable |
According to the paper, HRNet should have quite higher performance than OpenPose when trained and tested on COCO.
therefore it may have better performance than HRNet. @bpeck81 In the HRNet paper, authors state:
and
and
Therefore, I add a YOLOv3 detector to find person instances and then analyze them with HRNet. |
Thank you for answering the queries , As you said for multi person it does not work so good . Perhaps they will release new pretrained weights that would be better in performace. I tired on a |
At the moment, there is not an ID associated to each person because I didn't implement any person tracking functionality. |
@timtensor Could you please check the performance with the latest version of the code? |
@stefanopini i will try to test it in the coming days! |
Yes i notice much better performance and quite stable as well |
Hello
I was playing around with different videos and clips to check performance of how pretrained models work for both Hrnet and Openpose. I seem to notice the open pose seem to have a better accuracy ? Have you tried it , what is your opinion about it ?
The text was updated successfully, but these errors were encountered: