issues: 1322112135
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1322112135 | I_kwDOAMm_X85OzdSH | 6847 | Please expose __cuda_array_interface__ via the xarray.__array__() function if present | 8914493 | open | 0 | 5 | 2022-07-29T11:08:51Z | 2022-08-01T12:38:13Z | NONE | Is your feature request related to a problem?When using an array type with GPU support, such as CuPy arrays, Numba device arrays or Numba mapped arrays (shared), I'm using large NetCDF files which I wish to process against reference dataframes and use GPU acceleration to do this. For example, Numba mapped array: ```
When copied to xarray: ```
Array interface confirms same address for the base (CPU) array as above, i.e. Zero Copy ```
However the ```
AttributeError Traceback (most recent call last) Input In [23], in <cell line: 1>() ----> 1 data.array().cuda_array_interface AttributeError: 'numpy.ndarray' object has no attribute 'cuda_array_interface' ``` Describe the solution you'd likeExpose Describe alternatives you've consideredAs a workaround, I'm not using xarray for NetCDF files. Instead I'm converting them into an dictionary of arrays which provides me with the GPU interfaces. Additional contextNo response |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/6847/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | issue |