Resolving torch cuda availability for cpu-only installation #275
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dear OpenFold developers,
We encountered a
TypeError: expected string or bytes-like objecterror insetup.py, line 111when running pip install on a cpu-only machine. The currentsetup.pyresolves CPU/GPU environments based on CUDA_HOME, but for cpu installations of pytorch (v1.13.1) this variable is set to'/usr/local/cuda'by default. This caused pip install to proceed to compiling the cuda kernels.Here is a hotfix that ensures installing the cpu version when no cuda build of pytorch is detected.