Skip to content
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

Open
wangdong0556 opened this issue Nov 4, 2020 · 6 comments
Open

Find data #44

wangdong0556 opened this issue Nov 4, 2020 · 6 comments

Comments

@wangdong0556
Copy link

Thank you for providing this function. Where can I find name_of_input_pose. Json and result.json ? Can you provide the download address

@mks0601
Copy link
Owner

mks0601 commented Nov 4, 2020

you can use any 2D pose estimation methods to obtain name_of_inptu_pose.json. For example, here

@wangdong0556
Copy link
Author

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 '?

@metehkaya
Copy link

Can the file you provided here be directly used during training or testing? I guess, it is just a part of MS COCO json file, right? Because according to video, it seems that MS COCO compatible json file is actually larger.

@mks0601
Copy link
Owner

mks0601 commented Apr 24, 2022

That file is 2D pose estimation result of other 2D pose estimator, not a part of MSCOCO dataset.
You can train and test on that file, but the trained model will not be model-agnostic refiner, while the PoseFix is.

@metehkaya
Copy link

metehkaya commented Apr 24, 2022

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.

@mks0601
Copy link
Owner

mks0601 commented Apr 24, 2022

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants