issue_comments

Table actions

4 rows where author_association = "MEMBER" and issue = 735523592 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • Cannot plot multiindexed (stacked) coordinate as hue variable · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
929295038 https://github.com/pydata/xarray/issues/4562#issuecomment-929295038 https://api.github.com/repos/pydata/xarray/issues/4562 IC_kwDOAMm_X843Y-q- benbovy 4160723 2021-09-28T14:39:43Z 2021-09-28T14:39:43Z MEMBER

Note that we're planning to depreciate multi-index dimension (tuple) coordinates and keep only the multi-index levels as coordinates. The main reason is that this will better fit within Xarray's (forthcoming) updated data model with explicit indexes (so far we kept those tuple coordinates to make multi-index work with the concept of a "dimension" index coordinate, but this will no longer be necessary).

I see how convenient it is here to use those tuple coordinates as hue (legend) labels to show the value combinations, but there must be other ways to do that. For example, you could simply assign a new coordinate to the DataArray with tuple values (i.e., mi.values) without attaching any index to it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Cannot plot multiindexed (stacked) coordinate as hue variable  735523592
729275558 https://github.com/pydata/xarray/issues/4562#issuecomment-729275558 https://api.github.com/repos/pydata/xarray/issues/4562 MDEyOklzc3VlQ29tbWVudDcyOTI3NTU1OA== mathause 10194086 2020-11-17T23:27:47Z 2020-11-17T23:27:47Z MEMBER

You have to specify x as well: da.plot(hue='mi_idx1', x="x"). But yes, this is not ideal - would be nice to get this working with hue="mi".

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Cannot plot multiindexed (stacked) coordinate as hue variable  735523592
721855875 https://github.com/pydata/xarray/issues/4562#issuecomment-721855875 https://api.github.com/repos/pydata/xarray/issues/4562 MDEyOklzc3VlQ29tbWVudDcyMTg1NTg3NQ== mathause 10194086 2020-11-04T17:04:28Z 2020-11-04T17:04:28Z MEMBER

Yes seems a sems like a sensible approach. Maybe you can use hue="mi_idx1" and set the label manually as a workaround. (Can't test right now) 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Cannot plot multiindexed (stacked) coordinate as hue variable  735523592
721348538 https://github.com/pydata/xarray/issues/4562#issuecomment-721348538 https://api.github.com/repos/pydata/xarray/issues/4562 MDEyOklzc3VlQ29tbWVudDcyMTM0ODUzOA== mathause 10194086 2020-11-03T20:06:33Z 2020-11-03T20:06:33Z MEMBER

That might be my doing here: #3938 It makes sense to allow a MultiIndex as a label but probably not as a coordinate. So this may need some thinking. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Cannot plot multiindexed (stacked) coordinate as hue variable  735523592

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