issue_comments

Table actions

4 rows where issue = 307783090 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • max-sixty · 4 ✖

issue 1

  • rolling: allow control over padding · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
375850170 https://github.com/pydata/xarray/issues/2007#issuecomment-375850170 https://api.github.com/repos/pydata/xarray/issues/2007 MDEyOklzc3VlQ29tbWVudDM3NTg1MDE3MA== max-sixty 5635139 2018-03-24T06:16:29Z 2018-03-24T06:16:29Z MEMBER

2011 looks good - I didn't realize numpy already had pad

Agree with your other comments. Thanks as ever @fujiisoup 

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   rolling: allow control over padding 307783090
375810316 https://github.com/pydata/xarray/issues/2007#issuecomment-375810316 https://api.github.com/repos/pydata/xarray/issues/2007 MDEyOklzc3VlQ29tbWVudDM3NTgxMDMxNg== max-sixty 5635139 2018-03-23T22:03:24Z 2018-03-23T22:03:24Z MEMBER

@fujiisoup Yes for sure - I think it would be good. I think there are two salient questions: - Where this lives in the API: Should this be under construct? I don't think the kwarg should be called fill_value - that traditionally has a specific meaning of "the value to replace NaN with". I don't understand the periodic reference, but likely I'm missing something. Could be wrap=True, or roll=True? - How it's implemented - do you have a view here? Can you use the construct machinery? Or we make a new array and run rolling over it?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   rolling: allow control over padding 307783090
375484121 https://github.com/pydata/xarray/issues/2007#issuecomment-375484121 https://api.github.com/repos/pydata/xarray/issues/2007 MDEyOklzc3VlQ29tbWVudDM3NTQ4NDEyMQ== max-sixty 5635139 2018-03-22T22:56:09Z 2018-03-22T22:56:09Z MEMBER

Though I'm not sure you need the construct machinery.

IIUC you need to copy a window-sized amount of data from the front of the array onto the back.

You could do that with construct-like machinery, which would save a copy - though not a large copy

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   rolling: allow control over padding 307783090
375441040 https://github.com/pydata/xarray/issues/2007#issuecomment-375441040 https://api.github.com/repos/pydata/xarray/issues/2007 MDEyOklzc3VlQ29tbWVudDM3NTQ0MTA0MA== max-sixty 5635139 2018-03-22T20:09:54Z 2018-03-22T20:09:54Z MEMBER

ds.rolling(center=True, dayofyear=31).mean()

What do you mean by rolling here? As a reduce operation over a rolling window, like a moving average (rolling in xarray)? Or rolling around the end of a dataarray when shifting (roll in xarray)? Or a mix of both?

Specifically, what's the dayofyear=31 doing?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   rolling: allow control over padding 307783090

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