home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

5 rows where issue = 146287030 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 5

  • forman 1
  • shoyer 1
  • jhamman 1
  • magonser 1
  • stale[bot] 1

author_association 3

  • MEMBER 2
  • NONE 2
  • CONTRIBUTOR 1

issue 1

  • N-D rolling · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
458228295 https://github.com/pydata/xarray/issues/819#issuecomment-458228295 https://api.github.com/repos/pydata/xarray/issues/819 MDEyOklzc3VlQ29tbWVudDQ1ODIyODI5NQ== stale[bot] 26384082 2019-01-28T17:38:57Z 2019-01-28T17:38:57Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity If this issue remains relevant, please comment here; otherwise it will be marked as closed automatically

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  N-D rolling 146287030
208056716 https://github.com/pydata/xarray/issues/819#issuecomment-208056716 https://api.github.com/repos/pydata/xarray/issues/819 MDEyOklzc3VlQ29tbWVudDIwODA1NjcxNg== shoyer 1217238 2016-04-10T20:05:24Z 2016-04-10T20:05:24Z MEMBER

@magonser We could add support for strides, but for builtin operations like min, max, sum and mean, the implementation could not be any more efficient than doing the rolling window calculation first and then using indexing to select out the strides afterwards -- we already use one a pass algorithm (via bottleneck) that uses each data point once.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  N-D rolling 146287030
208022981 https://github.com/pydata/xarray/issues/819#issuecomment-208022981 https://api.github.com/repos/pydata/xarray/issues/819 MDEyOklzc3VlQ29tbWVudDIwODAyMjk4MQ== magonser 14014177 2016-04-10T17:34:26Z 2016-04-10T17:35:05Z CONTRIBUTOR

Hello together,

additional to forman's comments I would like to note that for the xarray rolling operation a stride would be useful in some use-cases. I have understood, that no work is currently planned, but wanted to leave this remark for further contributions.

I.e.

DataArray.rolling(min_periods=None, center=False, **windows)

with

windows={dimname: (size, stride=1)}

Thanks for xarray! It's great!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  N-D rolling 146287030
206429373 https://github.com/pydata/xarray/issues/819#issuecomment-206429373 https://api.github.com/repos/pydata/xarray/issues/819 MDEyOklzc3VlQ29tbWVudDIwNjQyOTM3Mw== forman 206773 2016-04-06T15:29:27Z 2016-04-06T15:29:27Z NONE

Thanks for the prompt reply!

Once we have decided to use xarray for our project(s) and once we familiarized with its internals, we'll be happy to contribute and support you! Currently we all feel a bit dizzy about the many options we have and how to decide which way to go: Create our own library using xarray or build on UK MetOffice's Iris, Apache OCW, or Max-Planck-Institute's CDO, etc.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  N-D rolling 146287030
206417958 https://github.com/pydata/xarray/issues/819#issuecomment-206417958 https://api.github.com/repos/pydata/xarray/issues/819 MDEyOklzc3VlQ29tbWVudDIwNjQxNzk1OA== jhamman 2443309 2016-04-06T15:04:55Z 2016-04-06T15:04:55Z MEMBER

@forman -

The main reason this isn't supported yet is that we haven't implemented it yet. I recently added the Rolling object to xarray and our initial application aimed to wrap the bottleneck moving window functions. Because the bottleneck moving window functions only supports one windowing axis, we have also adopted that constraint for now.

At this point, I don't know of any plans to extend this functionality although we could discuss further. The complexity of N-D rolling aggregations does increase a fair bit and we would ideally like to let a lower level package (e.g. bottleneck) handle most of that. Since you seem to have a tangible application for the N-D rolling feature, maybe this is something you want to contribute to?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  N-D rolling 146287030

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