Skip to content
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

Update Lasagne installation doc to new gpuarray backend #897

Open
dreamflasher opened this issue Feb 16, 2018 · 3 comments
Open

Update Lasagne installation doc to new gpuarray backend #897

dreamflasher opened this issue Feb 16, 2018 · 3 comments
Milestone

Comments

@dreamflasher
Copy link

The documentation at http://lasagne.readthedocs.io/en/latest/user/installation.html to verify cuda and cudnn installation is outdated. It currently yields: ValueError: You are tring to use the old GPU back-end. It was removed from Theano. Use device=cuda* now. See https://github.com/Theano/Theano/wiki/Converting-to-the-new-gpu-back-end%28gpuarray%29 for more information.
Unfortunately the documentation at Theano does not contain the information to verify cuda and cudnn installation.

@f0k f0k added this to the v0.3 milestone Feb 16, 2018
@f0k
Copy link
Member

f0k commented Feb 16, 2018

Yes, this documentation has not been updated for Theano 0.10+ yet, it will be updated at the latest when Lasagne drops support for Theano 0.8 (the last version of Theano that did not deprecate the old backend).
This being said, I can't find an equivalent for

THEANO_FLAGS=device=gpu python -c "import theano; print(theano.sandbox.cuda.device_properties(0))"

in the new backend. To verify whether cuDNN is available under the new backend, you can run:

python -c "from theano.gpuarray.dnn import dnn_present as d; print(d() or d.msg)"

@nouiz
Copy link

nouiz commented Feb 16, 2018 via email

@f0k
Copy link
Member

f0k commented Feb 16, 2018

If you use device=cuda for the new back-end, you have this printed during the import:

True, there's no need to query the device properties, simply importing Theano is enough to see whether the CUDA and cuDNN are used. The second command can still be useful for troubleshooting in case cuDNN is not being used.

I'm leaving this open since the documentation still needs to be updated later. (This requires more changes, it should include a section on libgpuarray/pygpu.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants