-
Notifications
You must be signed in to change notification settings - Fork 105
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
mesh_to_voxel - incorrect #3
Comments
Hi! Sorry for the trouble. I used this implementation with the ShapeNet dataset and I found that unfortunately not all of the meshes can be processed. In some cases, this is because the meshes are too far from anything that resembles a watertight mesh (although this approach can handle meshes with holes to an extent). You can improve the results somewhat by tweaking the parameters (this is a tradeoff between quality and computation time) and you can also try the depth-buffer based approach (this is a tradeoff between accuracy and number of blob artifacts). If you want to process the entire ShapeNet dataset, you can set the If you can provide the mesh files (or Shapenet ids) for these particular meshes, I can try to debug the process for them. |
I will try as you suggest! Thank you for your quick response and sorry for the late reply. |
I think that the new version works much better - great work!! |
Dear Marian, I would like to re-open the issue. I have a watertight mesh(hand mesh) and I tried to use mesh_to_vox(). But it gave unwanted reconstructions near the wrist. I tried to debug(but not successful) and what I found is that few of the voxel grid point's sdf values are miscalculated, this eventually makes marching cubes to wrongly reconstruct the surface. It would be a really great help if you could help me debug this issue. Thank you! |
Dear Marian, Thanks a lot for re-opening the issue. |
@anilesec I faced a similar problem. When using the |
Does someone know which shape classes from ShapeNet work well with |
FYI, using |
Dear Marian,
Thank you very much for releasing the code.
I've tried to pre-process the ShapeNet objects using your library. When I use mesh_to_voxel, the voxel representation is slightly different from the original object as below, or it has some unnecessary stuff appearing on edges.
I tried to tackle down what the problem was..(I guess it is probably related to getting the point clouds from the depth images during Scan) but I could not figure it out. So, I raise this issue to you.
Kind regards,
WB
The text was updated successfully, but these errors were encountered: