home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where author_association = "NONE", issue = 344093951 and user = 1882397 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

  • aseyboldt · 2 ✖

issue 1

  • DOC: add initial draft of a development roadmap for xarray · 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
409992634 https://github.com/pydata/xarray/pull/2309#issuecomment-409992634 https://api.github.com/repos/pydata/xarray/issues/2309 MDEyOklzc3VlQ29tbWVudDQwOTk5MjYzNA== aseyboldt 1882397 2018-08-02T16:45:44Z 2018-08-02T16:45:44Z NONE

I noticed and appreciate those plotting additions :-)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DOC: add initial draft of a development roadmap for xarray 344093951
409828598 https://github.com/pydata/xarray/pull/2309#issuecomment-409828598 https://api.github.com/repos/pydata/xarray/issues/2309 MDEyOklzc3VlQ29tbWVudDQwOTgyODU5OA== aseyboldt 1882397 2018-08-02T07:08:27Z 2018-08-02T07:08:27Z NONE

This roadmap sounds great! We plan on using xarray to store all traces in pymc4. The biggest item on my wish list for that is better support for plotting. I regularly convert traces to pandas and use the plotting functions there, or I convert it so that I can use seaborn. Better support for hierarchical indexes sounds useful as well. They can be a bit surprising right now, and they can't be serialised to netCDF. The documentation is quite important our use case. As it is, we are asking our users to learn Bayesian stats, diagnosing sampler issues and possibly some theano or tensorflow. When we switch to xarray, our users have to learn the basics of that as well. Most won't even have heard about netCDF. One thing in particular that I noticed is that many people seem to get confused about the difference between coordinates and dimensions at some point.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  DOC: add initial draft of a development roadmap for xarray 344093951

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