2018-04-25 06:25:21 -0600 | marked best answer | Start discussion for Opencv 4.0 feature I want to discuss a topic which I consider important for Opencv 4.0 (specifically: the maximum Matrix size: https://github.com/opencv/opencv/issues/10211). Can I just open a new discussion in the issues section: https://github.com/opencv/opencv/issues?q=milestone%3A4.0 or would this be considered rude? Since opencv 4.0 will break with binary compatibility anyway, this would be a good time to upgrade to a larger matrix size (with a size_t type instead of an int for the matrix size), imho. |
2018-04-23 03:40:34 -0600 | received badge | ● Student (source) |
2018-04-23 03:37:56 -0600 | edited question | Start discussion for Opencv 4.0 feature Start discussion for Opencv 4.0 feature I want to discuss a topic which I consider important for Opencv 4.0 (specificall |
2018-04-23 03:37:56 -0600 | received badge | ● Editor (source) |
2018-04-23 03:34:09 -0600 | asked a question | Start discussion for Opencv 4.0 feature Start discussion for Opencv 4.0 feature I want to discuss a topic which I consider important for Opencv 4.0 (specificall |
2017-07-11 03:51:43 -0600 | received badge | ● Enthusiast |
2017-07-03 05:57:09 -0600 | asked a question | Use OpenCL CPU Backend for custom kernel (Opencv 3.2) Hi, I want to choose a CPU backend for a custom opencl kernel. I tried context.create(cv::ocl::Device::TYPE_CPU), this tells me it uses the Intel CPU (context.device(0) is the Intel CPU), but the performance is completely identical to the performance using the GPU backend and the CPU usage is at 0-1%. Is there a way to force using the CPU backend? (I want to compare performance) Thanks in advance, Peter |