-
Notifications
You must be signed in to change notification settings - Fork 182
Description
A common use case is to do some computation on the GPU and then render the result in a display ( cupy/cupy#5711 ) ( vispy/vispy#1985 ) ( vispy/vispy#1986 ) ( napari/napari#2243 ). This could be an image that is shown or a plot or something else. Given the registration/unregistration and mapping/unmappaing of memory, this can generate quite a bit of boilerplate in Python ( vispy/vispy#2391 ), which in turn hinders adoption. Ideally some standard objections/functions could be supplied (ideally in CUDA Python) that users could leverage to prep data for rendering. Preferably they could use one function call to covert any __cuda_array_interface__
, __dlpack__
, etc. supporting object into one that can be used for rendering (and hang onto the lifetimes of any supporting buffers via RAII-style semantics)