issue_comments

Table actions

3 rows where author_association = "MEMBER" and issue = 697814535 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

issue 1

  • Enhanced plotting option (latex backend and/or unit change) · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
690348123 https://github.com/pydata/xarray/issues/4414#issuecomment-690348123 https://api.github.com/repos/pydata/xarray/issues/4414 MDEyOklzc3VlQ29tbWVudDY5MDM0ODEyMw== dcherian 2448579 2020-09-10T14:59:25Z 2020-09-10T14:59:25Z MEMBER

The plotting routines use da.attrs["long_name"] and da.attrs["units"].

For publication figures, I set these manually when reading data: da.attrs["long_name"] = "$J_q^t$" and da.attrs["units"] = "$W/m²$". Every plot after that is then nicely labeled.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Enhanced plotting option (latex backend and/or unit change) 697814535
690295612 https://github.com/pydata/xarray/issues/4414#issuecomment-690295612 https://api.github.com/repos/pydata/xarray/issues/4414 MDEyOklzc3VlQ29tbWVudDY5MDI5NTYxMg== keewis 14808389 2020-09-10T13:39:29Z 2020-09-10T13:39:29Z MEMBER

pint already supports printing units with latex, so you might be able to use pint and pint-xarray (and possibly cf-xarray for the definitions of degrees_north, etc.) in the future. See also xarray-contrib/pint-xarray#26.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Enhanced plotting option (latex backend and/or unit change) 697814535
690268138 https://github.com/pydata/xarray/issues/4414#issuecomment-690268138 https://api.github.com/repos/pydata/xarray/issues/4414 MDEyOklzc3VlQ29tbWVudDY5MDI2ODEzOA== fmaussion 10050469 2020-09-10T12:58:22Z 2020-09-10T12:58:22Z MEMBER

Thanks a lot for this suggestion! I'll let the others chime in as well, but there are a few things to consider here: - xarray's plotting capability is not meant to be "publication ready" but "as close as possible to the data". I.e. units like degrees_north, etc. have to stay like this because it unambiguously shows where the data came from and how users can access it from the file, etc. - in general, making the plots nicer with opinionated defaults like yours would be a nice addition to the xarray ecosystem. It could live in a separate package, and use the accessor syntax to extend xarray. For example, my own little extension works this way and does opinionated stuff with the accessor: https://salem.readthedocs.io 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Enhanced plotting option (latex backend and/or unit change) 697814535

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