-
Notifications
You must be signed in to change notification settings - Fork 18
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
Non-CUDA alternatives #16
Comments
I am currently on it to implement a pure C++ variant of the |
Hey Mirza, that's good to hear! |
Hello Amos, Regarding my question about the normalization, what I was missing, was the I am currently trying to implement the code in python just so I can make it easier to deploy on any machine, since I am currently using a weird setup utilizing a docker container with a specific CUDA version and a mounted instance of Matlab and X11 forwarding. To be also transparent about the project, I have also mentioned you in the credits and your paper to be cited ;) |
Hi Mirza,
Fair enough. If people need other functionality, they can still fall back to the Matlab version or port the functions to Python themselves. |
Right now, the user needs to have a setup with Matlab, CUDA and C++ compiler available to even test our software.
It would be great to have an alternative Matrix-Vector product that runs on the CPU only. This function will probably be slower than the current, but at least allow the user to test the software.
This could be achieved either by a Matlab script coupling_matrix_multiply_CPU.m or by a c++ file that does what coupling_matrix_multiply_CUDA.cu does (and which is compiled by mex).
The text was updated successfully, but these errors were encountered: