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

Getting weird results when training with custom data #50

Open
qzane opened this issue Oct 13, 2022 · 6 comments
Open

Getting weird results when training with custom data #50

qzane opened this issue Oct 13, 2022 · 6 comments

Comments

@qzane
Copy link

qzane commented Oct 13, 2022

prog_025000
I got this weird result, is it normal or did I do any wrong? I validate my camera parameters using cv2.projectPoints and they seems to be correct. Also, I have another dataset in which I got the body pose using EasyMocap, can I just use the 'pose' and 'Rh' data from them (I also checked the code in prepare_dataset.py and find that you actually don't need 'Th', right?

@Dipankar1997161
Copy link

@qzane,

Even I am getting weird results for my dataset when training. Did you generate your smpl values from ROMP/VIBE?

Maybe its the camera values or something wrong.
If you solved it, it would be great if you can provide some information on this.

I will be waiting for your response

prog_005000

@leviome
Copy link

leviome commented Jul 19, 2023

LOL, it seems I was not the only one getting this:
prog_040000

@StephenYangjz
Copy link

I am experiencing something similar with the results form 4D Humans. Has anyone solved this issue?

@Dipankar1997161
Copy link

I am experiencing something similar with the results form 4D Humans. Has anyone solved this issue?

That's because the projection of sampling rays isn't 100% accurate. So make sure you have the correct camera values.

@StephenYangjz
Copy link

I am experiencing something similar with the results form 4D Humans. Has anyone solved this issue?

That's because the projection of sampling rays isn't 100% accurate. So make sure you have the correct camera values.

I ran 4d humans on mocap just to verify, and I even tried to substitute the cam in/extrinsics by the mocap dataset gt. It still gave me similar results...

@Dipankar1997161
Copy link

I am experiencing something similar with the results form 4D Humans. Has anyone solved this issue?

That's because the projection of sampling rays isn't 100% accurate. So make sure you have the correct camera values.

I ran 4d humans on mocap just to verify, and I even tried to substitute the cam in/extrinsics by the mocap dataset gt. It still gave me similar results...

What do you mean by running mocap on it? Did you mean Easymocap?

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

4 participants