Josh Marshall

It looks like there is something wrong with a combination of the POCL runtime and using gpuMatrix. Given the it is all CPU based, it should behave identically to vclMatrix,...

Here are my final (cleaned up) results: ``` AMDGPU-PRO GPU memory run times: elapsed 0.341 elapsed 0.048 elapsed 0.258 elapsed 2.387 elapsed 27.039 elapsed 198.641 AMDGPU-PRO main memory run times:...

It looks like solve() as implemented in `src/solve.cpp` should be using viennaCL's `viennacl::linalg::opencl::inplace_solve` and the deep copy of the A matrix in R/solve.R:33 can be completely skipped. The implementations in...

cleaned up my test script for easier use: https://gist.github.com/74f6c584b501e617af0fc1d9a2707d98

@cdeterman Can you tell me how you run testthat for this project? I've been having a little difficulty and a few other projects to split my attention.

Just from R studio, to to run anything. It should be, but I'm missing something. I've read a few things off of google, but it just doesn't seem to be...

Still on my list, just deprioritized as I have to get other work out.

@prdm0 I have a few insights, but the author knows more. The big thing is that not all operations are directly supported by calling into GPU operations. Like in this...

Oh hey, mschu! If it is something related to conflicting macros, the RcppEigen to system stack works, and the cuda to system stack works, so I'm betting it is a...

@bobymathew Checking in at the following: https://launchpad.net/ubuntu/yakkety/amd64/nvidia-cuda-toolkit https://devtalk.nvidia.com/default/topic/975944/cuda-setup-and-installation/ubuntu-16-10-cuda-toolkit-install-with-opencl/ It is likely that you have a broken driver installation. Speaking from past systems, the closed source AMD and Nvidia drivers can...