-
Notifications
You must be signed in to change notification settings - Fork 26
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
ClTensor that cannot be copied back to CPU? #8
Comments
I believe you're loading cutorch after loading cltorch? Can you try loading cutorch first, and then loading cltorch? (cutorch monkey-patches the copy functions, and doesnt realize cltorch might have monkey-patched them too) (edit: that 'userdata' is a ClTensor, which is unrecognized by CudaTensor copy function) |
aah missed that, it works now, MNIST classification on HD Graphics:
|
Cool :-) By the way, we could modify the cutorch monkey-patching to allow loading in any order. But I guess I dont want to touch cutorch too much for now, in case I break something. You can see the monkey-patcher for cltorch here though: https://github.com/hughperkins/cltorch/blob/master/init.lua#L3-L34 Basically it saves the old functions, and calls those, unless it sees an incoming ClTensor, in which case it calls the new functions |
Hmmm, hey thats a pretty nice demo script you have there. |
there was a few things I had to patch in the script and in clnn, I can create issues on what needs to be done to support networks loaded with loadcaffe if you want |
Yes please, sounds good :-) |
I wanted to run a simple example with MNIST classification from here https://github.com/szagoruyko/loadcaffe/blob/master/examples/mnist_lenet.lua with cltorch, it runs fine after a few hacks but I cannot copy the output back to FloatTensor:
The text was updated successfully, but these errors were encountered: