issue_comments
3 rows where author_association = "MEMBER" and issue = 192248351 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- win_type for rolling() ? · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
263751396 | https://github.com/pydata/xarray/issues/1142#issuecomment-263751396 | https://api.github.com/repos/pydata/xarray/issues/1142 | MDEyOklzc3VlQ29tbWVudDI2Mzc1MTM5Ng== | jhamman 2443309 | 2016-11-30T01:04:21Z | 2016-11-30T01:10:24Z | MEMBER | Certainly open to adding this functionality. Bottleneck isn't going to help so the code will all live in xarray. I think it makes sense to have a bit of a design discussion here prior to getting started. Questions: 1. What window types are you interested in adding? Pandas includes:
2. Can we maintain compatibility with pandas and bottleneck.We have tried to maintain compatibility with both pandas and bottleneck in our rolling implementation. This is proving somewhat difficult (e.g. #1046) but is a design consideration that we should keep in mind. Also, our current implementation falls back to operating on individual slices of the DataArray when bottleneck cannot be utilized. We should think a bit about the applicability of other windows when using other window types. Presumably, each 3. What about nd windows?Our current implementation left open the possibility of n-dimensional windows (see #819). While we haven't implemented it yet, the utility of the rolling object for a 2+ dimensional smoother would be quite a nice feature. That said, I'd be hesitant to implement anything on the rolling object that would not allow us to make this addition in the future. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
win_type for rolling() ? 192248351 | |
263678778 | https://github.com/pydata/xarray/issues/1142#issuecomment-263678778 | https://api.github.com/repos/pydata/xarray/issues/1142 | MDEyOklzc3VlQ29tbWVudDI2MzY3ODc3OA== | max-sixty 5635139 | 2016-11-29T19:50:08Z | 2016-11-29T19:50:08Z | MEMBER | Think it would be useful generally. @jhamman will have a better view of how difficult it is to implement. Our use cases are fine with simple windows, although an One API choice is to what extent we want |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
win_type for rolling() ? 192248351 | |
263642547 | https://github.com/pydata/xarray/issues/1142#issuecomment-263642547 | https://api.github.com/repos/pydata/xarray/issues/1142 | MDEyOklzc3VlQ29tbWVudDI2MzY0MjU0Nw== | shoyer 1217238 | 2016-11-29T17:41:53Z | 2016-11-29T17:41:53Z | MEMBER | There are no immediate plans that I know of, but I think we are certainly open to adding this functionality if someone wants to look into it. cc @jhamman @MaximilianR |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
win_type for rolling() ? 192248351 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 3