-
Notifications
You must be signed in to change notification settings - Fork 8
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
Training with dataset THuman2.0 #2
Comments
We use the solution1 in our experiments. |
Thanks for your reply. Today I tried to calculate occ using the method you gave me. Since PIFu is obtained by uniform sampling and surface sampling, I used the sampling method in the source code and used pyrender to render the sample points. I found that the human mesh in the THumen2.0 dataset is too small and usually makes mistakes after training and the method you provided is also calculated by sampling points. I wonder how you solved this problem? Looking forward to your reply. |
@CastoHu In my opinion, there are three things that matter: 1. the image you rendered; 2. the projection matrix (calib); 3. the mesh (points). If the image and the calib are right, the mesh should be in the right size and place. So I think you should check them all. What do you mean by "human mesh in the THumen2.0 dataset is too small and usually makes mistakes after training"? |
What I actually mean is that the human body coordinates in the THuman2.0 dataset are normalized, whereas the data in the rp dataset used in the source code is raw. I tried a few things:
|
Hi,
Thanks for your new idea, I find that you trained the PIFu method with THuman2.0 Dataset. I also train it myself, but the results of the sdf are all 0. I think maybe it is because the mesh in THuman2.0 is not watertight. I wonder how you use THuman2.0 and Twindom dataset training PIFu method.
Looking forward to your reply.
Thanks.
The text was updated successfully, but these errors were encountered: