torch-mesh-isect is not compatible with your environment.yml

[VisionaryMind]

Thank you for publishing this code. It is quite intriguing! Unfortunately, torch-mesh-isect does not work with the environment.yml you have published. I presume it because of an incompatibility with CUDA versions greater than 9. I am unable to compile and install it with CUDA 10.2, and it would appear to be an issue for all v10 installations.

Is it possible to eliminate or workaround the torch-mesh-isect dependency? Perhaps use a similar (but more up-to-date) library?

[MoyGcc]

Hi, thank you for your kind words! I also encountered problems while I tried to install torch-mesh-isect for the first time (CUDA 10.2). And I found almost all of the solutions in vchoutas/torch-mesh-isect#23. Hope that could help you with the installation. And I can see there are also users have successfully made it run with quite new CUDA version vchoutas/torch-mesh-isect#27. So I guess it would not be a big problem.

In this project, we use torch-mesh-isect as a part of post-processing to remove artifacts produced during registration to SMPL with offsets. You can simply work around this library by skipping the smoothing step in the post-processing https://github.com/MoyGcc/hpcwild/blob/main/registration/smoothing.py. As a trade-off, you might need to increase the weight for Laplacian loss to avoid possible non-smoothness of the surface which will lead to a bit less-detailed result.

hpcwild/registration/smpl_registration/fit_SMPLD.py

Line 47 in dea76d7

'lap': lambda cst, it: 5. ** 4 * cst / (1 + it), # 10. ** 4 * cst / (1 + it) for HPC

Feel free to ask follow-up questions if you meet other issues.

[VisionaryMind]

Thank you for the prompt response. I was eventually able to get torch-mesh-isect installed by downgrading Conda cudatoolkit to 10.0. Looking at that code's README, they state it had only been tested up to 10.0. Perhaps it could be forced to work with Cuda 11+, but at least for now, I have a way forward.

[MoyGcc]

Cool! I will close this issue.