-
Notifications
You must be signed in to change notification settings - Fork 37
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
CUDA toolkit now provided via anaconda? #813
Comments
The numba version of |
Keep in mind that the toolkit isn't much use without the driver. You can't even compile, since libcuda.so comes with the driver, not the toolkit. |
I was under the impression we could use multiple toolkit versions if a recent driver (capable of supporting the most recent toolkit version) was installed. The big complaint we've had from users is that we might have compiled/released OpenMM conda packages against a CUDA version that is not available on their systems. Presuming we used a docker build environment with a recent CUDA driver, would it be possible to build several versions of the OpenMM conda package using these toolkit versions (7.5, 8.0, 9.0) and make packages for all three (with appropriate toolkit package dependencies) available that would run on a range of drivers? Presumably, only kernels that support the CUDA toolkit we used to compile would work, but I'm not sure if there is more precise matching of CUDA toolkit x driver x compiled code that needs to happen for this to work. |
I believe the requirement is that That's separate from the question of providing several different OpenMM packages compiled against different CUDA versions. We could do that either way. But as far as I know, conda can't detect what driver they have installed, so the user would have to manually specify which version they wanted. |
how to install cuda toolkit in anaconda |
try this it will detect your pc specs and install the required toolkits i guess! conda install -c anaconda cudatoolkit |
We don't officially support installing CUDA via conda, so this should be considered experimental. But I'd love to see if we could get this to work. Can you do a "conda list" and paste all the packages you have installed here? And which platform are you on? Sounds like win? |
I am using win 7. I created this environment to run a tf code. I installed tf 1.4, cuda 8.0 and cudnn 6.0 using anaconda. packages in environment at C:\ProgramData\Anaconda3\envs\tfenv: Name Version Build Channel |
The error is as shown below. I know that I need to set the paths but one of the reasons why I was trying to install cuda using anaconda was because in some way, I was getting error when I tried to install cuda 8.0 from the exe file downloaded from nvidia. Since cudnn64_6.dll is included with 'cudnn-8.0-windows7-x64-v6.0' , I guess this dll should be somewhere inside anaconda folder after I installed the package, right? In case I keep the cuda and cudnn packages installed and install the cuda and cudnn using nvidia files in my computer, which one will be used for the environment when running the script? (tfenv) C:\Program Files (x86)\Python 3.5.2\tensorflow\Master - Mask_RCNN>python During handling of the above exception, another exception occurred: Traceback (most recent call last): |
OK, a few things here:
I think the anaconda channel
Good luck! |
Extending the issues with conda installation of cudatoolkit. I dont really see the nvcc binary (or cuda-gdb, nvvp, etc) tools installed when using conda. |
I don't think there's a supported mechanism for installing the CUDA toolkit via conda at this time. The best approach I've seen seems to be pytorch, which uses dummy packages to indicate which version of CUDA you've installed: https://anaconda.org/pytorch/repo |
Summary of steps I've done to install tensorflow-gpu in Ubuntu 18.04 (should work in any Debian-based distro). 1.Install Nvidia driver on a machine with supported Nvidia card. $ sudo prime-select nvidia https://repo.anaconda.com/archive/Anaconda3-5.2.0-Linux-x86_64.sh (Don’t use python 3.7.)
$ conda install tensorflow-gpu==1.11 cudatoolkit==9.0 cudnn==7.1.2 h5py
|
@nospotfer this works! Thanks very much! |
Guys, I don't get it, how do I get the nvcc comand to work on anaconda? It just says it's unreconginsed? |
@deama : We haven't yet migrated to installation of the CUDA tookit via |
Since we last checked, there are now more @peastman: For building nightly development packages of OpenMM, do you think CUDA 9.2 and 10.0 would be sufficient? |
That seems fine. |
Would following that nvidia guide work for me if I'm on windows using anaconda? |
@deama : Yes, that is how we intend it to work for now. Note that the NVIDIA installer will install the CUDA Toolkit at the system level, rather than in anaconda, but the OpenMM package you install via |
Hi, found my way here via googling. I work on summit/titan where there are cuda or cudatoolkit modules. I am wondering how the cudatoolkit conda package interacts with these. Is the package just a wrapper around the existing libraries, so that path/environment resolution is easier? Earlier it is mentioned that the package can be used to get tensorflow up and running on an ubuntu system. how would this translate to an hpc environment with pytorch? Here we do not have sudo, and the gpu's are not accessible at install time (often the gpu nodes are behind a firewall). Also the install paths are non standard and environmental variables are often renamed, how does the package actually find the system CUDA compiler? My main reason for asking is 'nccl', titan does not seem to have nccl installed and getting it installed on a cray system is proving challenging. Sometimes getting any thing compiled on cray/power system is challenging, so conda has been a great help. Sorry for the long post and all the questions. |
@zeneofa: We don't yet have access to Summit, but on Titan, you can simply load a CUDA toolkit module (7.5 or 9.2) and then install the corresponding version of OpenMM, where we have built a separate package for each CUDA version (7.5 through 10.0) that can be selected via a conda channel label, e.g.: conda install -c conda-forge -c omnia -c omnia/label/cudaXY openmm where For It looks like it doesn't include conda install nccl though this is only built for a few CUDA versions. Some other versions have been compiled and pushed to anaconda cloud:
Amen! |
thanks for the info. Will look into that. One of my main problems with using conda packages on titan/rhea/eos and other hpc environment is the incompatibility GLIBC error that often pops up. So far the only way around this I have found is to recompile from scratch. Hence my current issues with getting pytorch working on Titan. I will dig around the recipes, thanks again. |
To answer about the error posted by fastlater. I had to install tensorflow outside anaconda and run my programs with visual studio, ran fine.. trying to resolve problem in anaconda now(windows7) |
@1961ned Is there any update about this problem in anaconda on win7? |
nothing yet |
I installed cudatoolkit (10.0.130) in my computer via anaconda.
What's appears to be wrong? |
I just noticed that anaconda now appears to provide packages for different CUDA toolkit versions.
The text was updated successfully, but these errors were encountered: