home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where issue = 866826033 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

  • dcherian 1
  • max-sixty 1
  • mathause 1

issue 1

  • Add an Cumulative aggregation, similar to Rolling · 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
826374418 https://github.com/pydata/xarray/issues/5215#issuecomment-826374418 https://api.github.com/repos/pydata/xarray/issues/5215 MDEyOklzc3VlQ29tbWVudDgyNjM3NDQxOA== max-sixty 5635139 2021-04-25T19:10:36Z 2021-04-25T19:10:36Z MEMBER

.cumulative is great! Much better.

The benefit is that the API surface is reduced — e.g. we can have a .cumulative().integrate(), rather than a separate .cumulative_integrate (and so on, for each aggregation), from https://github.com/pydata/xarray/pull/5153.

The implementation could be as simple as da.rolling(dim=da.sizes[dim]). How compatible would dask be with that? How does it compare to the numpy.ufunc.accumulate(...) suggestion?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add an Cumulative aggregation, similar to Rolling 866826033
826364666 https://github.com/pydata/xarray/issues/5215#issuecomment-826364666 https://api.github.com/repos/pydata/xarray/issues/5215 MDEyOklzc3VlQ29tbWVudDgyNjM2NDY2Ng== dcherian 2448579 2021-04-25T18:05:55Z 2021-04-25T18:05:55Z MEMBER

IIUC da.expanding(dim=dim).sum() is da.cumsum(dim) with support for min_periods and center like rolling.

I guess all expanding reductions are basically numpy.ufunc.accumulate(...). The dask versions will be "interesting" to write. https://github.com/dask/dask/blob/f1f37cae96d5e98f8043ea430539a4fffbe62661/dask/array/reductions.py#L1389-L1413

Like @mathause I find "expanding" confusing. .accumulate().sum() or .cumulative().sum() sounds much better to me.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add an Cumulative aggregation, similar to Rolling 866826033
826345774 https://github.com/pydata/xarray/issues/5215#issuecomment-826345774 https://api.github.com/repos/pydata/xarray/issues/5215 MDEyOklzc3VlQ29tbWVudDgyNjM0NTc3NA== mathause 10194086 2021-04-25T15:49:56Z 2021-04-25T15:49:56Z MEMBER

I don't entirely get what the function is supposed to do (even after looking at the pandas docstring) - can you give a an example or two?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add an Cumulative aggregation, similar to Rolling 866826033

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