Closed nikhilchh closed 1 month ago
Same problem when i try to reproduce the author's environment. You may need an environment compatible with your cuda
I installed torch with its own cuda
Now I face a new issue when i try to install the submodule: pip install -e submodules/custom-bg-depth-diff-gaussian-rasterization
While Running command Getting requirements to build editable Issue: ModuleNotFoundError: No module named 'torch'
I have checked manually that torch is installed in the env and is working.
Finally resolved the issue by
conda create -n GaussianTalker python=3.7
conda activate GuassianTalker
conda install pytorch==1.13.1 torchvision==0.14.1 torchaudio==0.13.1 pytorch-cuda=11.7 -c pytorch -c nvidia
Commented the torch, torchvision, torchaudio from requirements.txt
pip install -r requirements.txt
pip install -e submodules/custom-bg-depth-diff-gaussian-rasterization
Hey, I am still having this issue, what is your OS and what are its configurations?
Did someone face this issue while running
"pip install -e submodules/custom-bg-depth-diff-gaussian-rasterization"
Obtaining file:///home/nikhil/GaussianTalker/submodules/custom-bg-depth-diff-gaussian-rasterization Preparing metadata (setup.py) ... error error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully. │ exit code: 1 ╰─> [23 lines of output] Traceback (most recent call last): File "/home/nikhil/anaconda3/envs/GaussianTalker/lib/python3.7/site-packages/torch/init.py", line 172, in _load_global_deps ctypes.CDLL(lib_path, mode=ctypes.RTLD_GLOBAL) File "/home/nikhil/anaconda3/envs/GaussianTalker/lib/python3.7/ctypes/init.py", line 364, in init self._handle = _dlopen(self._name, mode) OSError: /home/nikhil/anaconda3/envs/GaussianTalker/lib/python3.7/site-packages/torch/lib/../../nvidia/cublas/lib/libcublas.so.11: undefined symbol: cublasLtGetStatusString, version libcublasLt.so.11
note: This error originates from a subprocess, and is likely not a problem with pip. error: metadata-generation-failed
× Encountered error while generating package metadata. ╰─> See above for output.
note: This is an issue with the package mentioned above, not pip. hint: See above for details.