issue_comments

Table actions

5 rows where author_association = "NONE", issue = 116349205 and user = 315810 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

  • mwaskom · 5 ✖

issue 1

  • More control on cmap params · 5 ✖

author_association 1

  • NONE · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
156863563 https://github.com/pydata/xarray/pull/655#issuecomment-156863563 https://api.github.com/repos/pydata/xarray/issues/655 MDEyOklzc3VlQ29tbWVudDE1Njg2MzU2Mw== mwaskom 315810 2015-11-15T22:18:13Z 2015-11-15T22:18:13Z NONE

Oh, sorry. LGTM.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   More control on cmap params 116349205
155884053 https://github.com/pydata/xarray/pull/655#issuecomment-155884053 https://api.github.com/repos/pydata/xarray/issues/655 MDEyOklzc3VlQ29tbWVudDE1NTg4NDA1Mw== mwaskom 315810 2015-11-11T19:21:01Z 2015-11-11T19:21:01Z NONE

The only safe times to assume a diverging colormap is when vmin = -vmax or when center is not None. If you want a diverging colormap for other situations, you need to specify cmap in the plot call.

That's fine for xray to have that opinion. Unfortunately, I think it's going to mean the behavior is going to diverge (heh) from what happens in seaborn.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   More control on cmap params 116349205
155820962 https://github.com/pydata/xarray/pull/655#issuecomment-155820962 https://api.github.com/repos/pydata/xarray/issues/655 MDEyOklzc3VlQ29tbWVudDE1NTgyMDk2Mg== mwaskom 315810 2015-11-11T15:42:15Z 2015-11-11T16:05:35Z NONE

That's the behavior I would want seaborn to have, but I guess @shoyer can weigh in too since it affects xray as well.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   More control on cmap params 116349205
155819176 https://github.com/pydata/xarray/pull/655#issuecomment-155819176 https://api.github.com/repos/pydata/xarray/issues/655 MDEyOklzc3VlQ29tbWVudDE1NTgxOTE3Ng== mwaskom 315810 2015-11-11T15:35:16Z 2015-11-11T15:35:16Z NONE

I think that if nothing else than preserving some backwards compatibility, you should take the route that shoyer suggested and assume that data spanning 0 with center not explicitly set and at most one of the limits specified should get a diverging palette.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   More control on cmap params 116349205
155814771 https://github.com/pydata/xarray/pull/655#issuecomment-155814771 https://api.github.com/repos/pydata/xarray/issues/655 MDEyOklzc3VlQ29tbWVudDE1NTgxNDc3MQ== mwaskom 315810 2015-11-11T15:23:12Z 2015-11-11T15:23:12Z NONE

It seems like this will use sequential logic if you set center to a value and only one of vmin or vmax? I would think in that case it looks like the user is asking for a diverging palette.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   More control on cmap params 116349205

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