issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 396084551 and user = 6815844 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

  • fujiisoup · 2 ✖

issue 1

  • rolling_exp (nee ewm) · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
454164295 https://github.com/pydata/xarray/pull/2650#issuecomment-454164295 https://api.github.com/repos/pydata/xarray/issues/2650 MDEyOklzc3VlQ29tbWVudDQ1NDE2NDI5NQ== fujiisoup 6815844 2019-01-14T21:16:08Z 2019-01-14T21:16:08Z MEMBER

@max-sixty

The error is when applying over a dimension on a dataset where only some of the variables have the dimension;

I remember I faced the same issue in implementing differentiate, interp, trapz, etc... and manually wrote the same logic for several times.

If it's helpful to add that functionality directly to apply_ufunc, lmk.

I think it would make the code much cleaner at least for these methods.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   rolling_exp (nee ewm) 396084551
452183122 https://github.com/pydata/xarray/pull/2650#issuecomment-452183122 https://api.github.com/repos/pydata/xarray/issues/2650 MDEyOklzc3VlQ29tbWVudDQ1MjE4MzEyMg== fujiisoup 6815844 2019-01-08T05:46:50Z 2019-01-08T05:46:50Z MEMBER

I like window_type / weighting argument to Rolling. But a little concern is whether it matches to the current API, such as __iter__.

BTW, does ewm computes the window mean based on index or coordinate value?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   rolling_exp (nee ewm) 396084551

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