home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

4 rows where issue = 476103888 and user = 2818208 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • gwgundersen · 4 ✖

issue 1

  • DataArray.set_index throws error on documented input · 4 ✖

author_association 1

  • CONTRIBUTOR 4
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
522344162 https://github.com/pydata/xarray/issues/3176#issuecomment-522344162 https://api.github.com/repos/pydata/xarray/issues/3176 MDEyOklzc3VlQ29tbWVudDUyMjM0NDE2Mg== gwgundersen 2818208 2019-08-18T18:27:15Z 2019-08-18T18:27:15Z CONTRIBUTOR

Looks like the idea of a glossary is already being discussed in https://github.com/pydata/xarray/issues/2410.

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DataArray.set_index throws error on documented input 476103888
521980573 https://github.com/pydata/xarray/issues/3176#issuecomment-521980573 https://api.github.com/repos/pydata/xarray/issues/3176 MDEyOklzc3VlQ29tbWVudDUyMTk4MDU3Mw== gwgundersen 2818208 2019-08-16T11:39:56Z 2019-08-16T11:39:56Z CONTRIBUTOR

Thanks for these answers! On a related point, I'd be keen to open a PR for improved documentation for whatever object a is. It seems like the documented Xarray terminology is "multidimensional coordinate", right? To me, "non-index coordinate" and "multidimensional coordinate" are both pretty vague until you're more familiar with Xarray's way of thinking.

What do you think of the terminology "alternative" or "auxiliary" dimension? a is clearly a dimension in the sense that it has coordinates or labels for all the "tick marks" along the x dimension. At the very least, I'd love to add a lot more examples of how to actually use these things.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DataArray.set_index throws error on documented input 476103888
521822644 https://github.com/pydata/xarray/issues/3176#issuecomment-521822644 https://api.github.com/repos/pydata/xarray/issues/3176 MDEyOklzc3VlQ29tbWVudDUyMTgyMjY0NA== gwgundersen 2818208 2019-08-15T22:42:07Z 2019-08-15T22:42:07Z CONTRIBUTOR

Looking at this now, and I'm a little surprised at the verbiage. In your example, do you consider a to be a "variable"? I thought variables were individual DataArray objects "inside" Dataset objects. My colleagues and I have been referring to objects such as a as "alternative" or "auxiliary" dimensions. Basically, a different labeling of the same coordinates. You also seem to call these "multidimensional coordinates"?

But I do think I see the use case. The point is that you can take an existing dimension's coordinates and set them as the coordinates for an alternative dimension?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DataArray.set_index throws error on documented input 476103888
521554109 https://github.com/pydata/xarray/issues/3176#issuecomment-521554109 https://api.github.com/repos/pydata/xarray/issues/3176 MDEyOklzc3VlQ29tbWVudDUyMTU1NDEwOQ== gwgundersen 2818208 2019-08-15T08:05:39Z 2019-08-15T08:05:39Z CONTRIBUTOR

Thanks for the explanation. I'll create a PR and link to this issue this evening.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DataArray.set_index throws error on documented input 476103888

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]);
Powered by Datasette · Queries took 16.613ms · About: xarray-datasette