result is very bad

Question

result is very bad

lianNice opened this issue 3 years ago · 7 comments

lianNice commented 3 years ago

test mpv datasets, but result is very bad?

Answer 1 · 2021-12-06T14:49:32.000Z

Hello,

I'll take a look at your codebase if you'll send it along. I suspect something has gone awry with your parser.

-Alex

Answer 2 · 2021-12-08T12:52:40.000Z

test mpv datasets, but result is very bad?

Hi,

Can your show the image id in your test cases? I will try to analyze the reason for the bad results.

-Zhenyu

Answer 3 · 2021-12-16T08:42:28.000Z

Hi. I generated similar results and I found that the wrong pre-processing causes them. Could you please release some samples to understand the pre-processing better?

Answer 4 · 2022-02-11T08:50:52.000Z

Here is my result on MPV test set. The result is also not good.
During the preprocess, the official openpose model obtains 25 keypoints, while the authors only use 18 keypoints? Is this preprocess step error that causes the bad results?

Answer 5 · 2022-02-25T03:31:02.000Z

obtains 25 keypoints, while the authors only use 18 keypoints? Is this preprocess step error that causes the bad results?

I guess it is the parsing error of the first person that causes such a bad result. Please check whether the inputs of the network are all right.

Answer 6 · 2022-03-26T11:55:54.000Z

I encountered similar issue. any updates? Thanks.

Answer 7 · 2022-09-07T02:23:29.000Z

This is due to the fact that openpose has two different versions of 18 and 25 keypoints, the code uses the 18 version, just rearrange the 25 points.