home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where issue = 1368027148 and user = 19285200 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

  • ghiggi · 2 ✖

issue 1

  • xarray imshow and pcolormesh behave badly when the array does not contain values larger the BoundaryNorm vmax · 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
1448588687 https://github.com/pydata/xarray/issues/7014#issuecomment-1448588687 https://api.github.com/repos/pydata/xarray/issues/7014 IC_kwDOAMm_X85WV7WP ghiggi 19285200 2023-02-28T17:33:46Z 2023-02-28T17:34:24Z NONE

@veenstrajelmer I am not sure I understand what you are saying. In the example I pass only norm to the plotting function ... As suggested by @kmuehlbauer the solution to this issue is to specify the extend argument in both the plotting call and cbar_kwargs. In the example, extend was only defined in cbar_kwargs (since is an argument also of mpl.Figure.colorbar). Likely we should align the arguments somewhere in the code with something like this:

if extend is None and cbar_kwargs.get("extend) is not None: extend = cbar_kwargs.get("extend) if extend is not None and "extend" not in cbar_kwargs cbar_kwargs["extend"] = extend

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  xarray imshow and pcolormesh behave badly when the array does not contain values larger the BoundaryNorm vmax 1368027148
1446791387 https://github.com/pydata/xarray/issues/7014#issuecomment-1446791387 https://api.github.com/repos/pydata/xarray/issues/7014 IC_kwDOAMm_X85WPEjb ghiggi 19285200 2023-02-27T17:58:15Z 2023-02-27T22:22:44Z NONE

Thanks to all the people above that have started digging into the problem ! @veenstrajelmer : Adding the levels=levels argument (together with norm, ... or dropping norm) does not correct/change the output figure. Of course commenting #da1.data[da1.data>=norm.vmax] = norm.vmax - 1 "solves" the issue, but this line of code is what enables to show up the bug, which is occurring when the array does not contain any value equal to or higher than norm.vmax

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  xarray imshow and pcolormesh behave badly when the array does not contain values larger the BoundaryNorm vmax 1368027148

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 14.694ms · About: xarray-datasette