issue_comments

Table actions

2 rows where author_association = "NONE" and issue = 1322112135 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

issue 1

  • Please expose __cuda_array_interface__ via the xarray.__array__() function if present · 2 ✖

author_association 1

  • NONE · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1201147133 https://github.com/pydata/xarray/issues/6847#issuecomment-1201147133 https://api.github.com/repos/pydata/xarray/issues/6847 IC_kwDOAMm_X85HmAz9 MurrayData 8914493 2022-08-01T12:38:12Z 2022-08-01T12:38:12Z NONE

Do you have to go through __array__ (see #6845) or would accessing the underlying array using DataArray.data work for you?

We could also add some properties under the DataArray.cupy namespace for convenience (See https://github.com/xarray-contrib/cupy-xarray)

It'd be good to see a minimal example showcasing the operations you'd like to work. This would also make a great contribution to https://cupy-xarray.readthedocs.io/

Yes, I'll share a workflow example shortly. Ideally I'd like it to be agnostic, rather than CuPy, for example using Numba mapped arrays for arrays which are larger then GPU RAM. I have several which are a lot larger then the 48GB on the RTX8000 GPUs I'm using for this. I have a mix of a dataframe with points of interest, spatial references tables for coordinate transformation (similar to NTv2 grids), and then use interpolation to estimate characteristics from data in a NetCDF file around the local points of interest. At present I have a workaround where I convert the NetCDF file into a dictionary of arrays which is pickled. The image below shows the mapped output of this process on UK rainfall in 2019 (Data source: UK Met Office) 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Please expose __cuda_array_interface__ via the xarray.__array__() function if present 1322112135
1201138802 https://github.com/pydata/xarray/issues/6847#issuecomment-1201138802 https://api.github.com/repos/pydata/xarray/issues/6847 IC_kwDOAMm_X85Hl-xy MurrayData 8914493 2022-08-01T12:30:26Z 2022-08-01T12:30:26Z NONE

I think ideally you could pass a DataArray to something that takes GPU arrays (like Numba kernels). If that doesn't make sense then perhaps passing the DataArray.data would be simpler. @rabernat made some interesting points on Twitter around not doing this though.

My thoughts were similar until I read @rabernat's comments as well and I see his point. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Please expose __cuda_array_interface__ via the xarray.__array__() function if present 1322112135

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);