-
Notifications
You must be signed in to change notification settings - Fork 64
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
Find data #44
Comments
you can use any 2D pose estimation methods to obtain |
Thank you for your reply, but I can't jump when I click 'here'. In addition, I saw in 'TF-Simplehumanpose' that someone asked how to find 'human_detection. Json', but it showed 'Closed this on 6 Feb 2019', 'name_of_input_pose' and 'name_of_inptu_pose' are the same?Is' result.json '2D result of' name_of_input_pose. Json '? |
That file is 2D pose estimation result of other 2D pose estimator, not a part of MSCOCO dataset. |
I am aware that the data you provided is not a part of MSCOCO dataset. Actually what I ask is that should that file follow MS COCO format completely. I guess not, because you don't make COCO(name_of_inptu_pose.json) at input_pose_load function like you did at COCO(self.test_annot_path) at load_annot function. |
Sure. The file format of that file follows 2D pose estimation output format, used to evaluate it by COCO evaluation API. The file format is completely different from COCO(self.test_annot_path) |
Thank you for providing this function. Where can I find name_of_input_pose. Json and result.json ? Can you provide the download address
The text was updated successfully, but these errors were encountered: