Cyrille Rossant

http://orcid.org/0000-0003-2069-9093

[Here is an interesting link](https://software.intel.com/en-us/articles/opencl-and-opengl-interoperability-tutorial). The first step will be to make this interop work by using raw OpenGL/OpenCL API calls. The second step will be to create abstraction classes...

Some additional notes. OpenGL/OpenCL interoperability is really tricky, and many drivers do not support it well. It's also difficult to set up the GPU drivers and OpenCL SDK correctly on...

> I'm doing a couple days of GPGPU training hosted by nVidia next week. I'll ask questions there.. Any news on this @lcampagn?

More generally I'm wondering if the collections system can buy us an automatic system that allows for heterogeneous values for all visual properties.

OK so we'll have to write custom code for markers, but for the other properties it would be nice to have an automatic system eventually. We can discuss that during...

This is a low-priority (read: "gadget"!) feature that may be useful in the future. In any interactive application, you need to move objects/cameras around. In most cases, you can do...

Here are a few use cases: - When zooming with the wheel (e.g. in a 3D scene), instead of changing abruptly from `z0` to `z1`, the zoom level could change...

@djhoese yeah there are ways to do GL-CUDA and Vulkan-CUDA interop without unnecessary array copying! With Vulkan you can even more simply use compute shaders, I think they're more limited...

I would advocate for a simple system where shaders are mostly fixed. Dynamically-generated shaders require a much higher degree of complexity. Eventually it all comes down to the functionality needed...