In case this might help others with a similar issue, I am posting a solution to a problem that I encountered when I first attempted to install Boltz2 in a new conda environment on a Linux workstation with an Nvidia RTX A6000 GPU and running CUDA 13.2. With this setup, there were errors related to the CUDA version and associated libraries. I got a working installation with the following strategy:
-
Remove the boltz2 conda environment.
-
Create a new boltz conda environment with python=3.12
-
Install PyTorch for CUDA 13.2 by using the nightly builds:
pip3 install --pre torch torchvision --index-url https://download.pytorch.org/whl/nightly/cu132
-
Install boltz2 without installing the default torch and cuda packages:
pip3 install boltz --no-deps
-
Install other required dependencies:
pip3 install boltz[cuda]
This procedure yielded a working boltz2 installation. It ran inferences that completed without frank errors. However, there were some warnings. I will post a sample output in a separate issue to ask for suggestions about how to remove the warnings or if they can be safely irgnored.
In case this might help others with a similar issue, I am posting a solution to a problem that I encountered when I first attempted to install Boltz2 in a new conda environment on a Linux workstation with an Nvidia RTX A6000 GPU and running CUDA 13.2. With this setup, there were errors related to the CUDA version and associated libraries. I got a working installation with the following strategy:
Remove the boltz2 conda environment.
Create a new boltz conda environment with python=3.12
Install PyTorch for CUDA 13.2 by using the nightly builds:
pip3 install --pre torch torchvision --index-url https://download.pytorch.org/whl/nightly/cu132
Install boltz2 without installing the default torch and cuda packages:
pip3 install boltz --no-deps
Install other required dependencies:
pip3 install boltz[cuda]
This procedure yielded a working boltz2 installation. It ran inferences that completed without frank errors. However, there were some warnings. I will post a sample output in a separate issue to ask for suggestions about how to remove the warnings or if they can be safely irgnored.