issue_comments

Table actions

1 row where issue = 301657312 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

  • einsum for xarray · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
369971985 https://github.com/pydata/xarray/issues/1951#issuecomment-369971985 https://api.github.com/repos/pydata/xarray/issues/1951 MDEyOklzc3VlQ29tbWVudDM2OTk3MTk4NQ== shoyer 1217238 2018-03-02T16:24:44Z 2018-03-02T16:24:44Z MEMBER

I like the idea of an einsum wrapper for xarray. This would probably be straightforward to build on top of the apply_ufunc machinery. I wouldn't worry about the lack of einsum for dask yet -- the linked dask issue already has several implementations, so we could easily add that later if desired.

There are at least two versions of this: - A dim argument for DataArray.dot that indicates which dimension(s) to sum over. - A function for applying this to many arrays simultaneously. Maybe xarray.dot(da1, da2, da3, dims=['x', 'y'])? This would use einsum internally but we don't need to specify the input dimensions again because we already have them on the DataArray objects.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   einsum for xarray 301657312

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]);