Re: [PyOpenCL] running on Xeon Phi

2015-07-19 Thread Sven Warris
Hi, I managed to get pyOpenCl working. Apparently, when I select the device 'by hand' all works fine: device = cl.get_platforms()[0].get_devices()[1] ctx = cl.Context(devices=[device]) queue = cl.CommandQueue(ctx) I've attached my demo script to this e-mail. It prints out some device info

Re: [PyOpenCL] AMD + pyopencl

2017-08-04 Thread Sven Warris
Hi Andreas, Thanks for the answer! Sounds very logical. I've added your explanation and suggestions to the github issue page. Best, Sven Op 4-8-2017 om 18:13 schreef Andreas Kloeckner: Hi Sven, Sven Warris <s...@warris.nl> writes: A user of my application has difficulty r

[PyOpenCL] AMD + pyopencl

2017-08-04 Thread Sven Warris
Dear all, A user of my application has difficulty running the software: https://github.com/swarris/Pacasus/issues/3 It seems to be related to the installation of (py)opencl and the AMD SDK. Google was not very helpful in this. And I don't have access to a machine with AMD CPUs to test the

Re: [PyOpenCL] GPU speed wrt number of threads

2018-06-06 Thread Sven Warris
Hi Aseem, This maybe caused by memory access collisions and/or lack of coalesced memory access. This technical report gives some pointers: https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-143.pdf Do you use atomic operations? Or maybe you have too many thread fences? I have no

Re: [PyOpenCL] “comparison of integers of different signs” Problem

2018-12-03 Thread Sven Warris
Dear Devin, I think this is because you are using an int to index an array. Using the index of an array is pointer arithmetic, which means with a[i] technically you are performing a+i. And the pointer a is of type unsigned long and i of type int, which gives this warning of type conversion