issue_comments
4 rows where author_association = "MEMBER" and issue = 675482176 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Optimize ndrolling nanreduce · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1507213204 | https://github.com/pydata/xarray/issues/4325#issuecomment-1507213204 | https://api.github.com/repos/pydata/xarray/issues/4325 | IC_kwDOAMm_X85Z1j-U | dcherian 2448579 | 2023-04-13T15:56:51Z | 2023-04-13T15:56:51Z | MEMBER | Over in https://github.com/pydata/xarray/issues/7344#issuecomment-1336299057 @shoyer
After some digging, this would involve using "summed area tables" which have been generalized to nD, and can be used to compute all our built-in reductions (except median). Basically we'd store the summed area table (repeated This would be an intermediate level project but we could implement it incrementally (start with cc @aulemahal |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Optimize ndrolling nanreduce 675482176 | |
716399575 | https://github.com/pydata/xarray/issues/4325#issuecomment-716399575 | https://api.github.com/repos/pydata/xarray/issues/4325 | MDEyOklzc3VlQ29tbWVudDcxNjM5OTU3NQ== | mathause 10194086 | 2020-10-26T08:40:51Z | 2021-02-18T15:39:40Z | MEMBER | This is already done for This should work for most of the reductions (and is a bit similar to what is done in
I think this should not be too difficult, the thing is that rolling itself is already quite complicated |
{ "total_count": 2, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 2, "rocket": 0, "eyes": 0 } |
Optimize ndrolling nanreduce 675482176 | |
741734592 | https://github.com/pydata/xarray/issues/4325#issuecomment-741734592 | https://api.github.com/repos/pydata/xarray/issues/4325 | MDEyOklzc3VlQ29tbWVudDc0MTczNDU5Mg== | mathause 10194086 | 2020-12-09T12:17:15Z | 2020-12-09T12:17:15Z | MEMBER | I just saw that numpy 1.20 introduces |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Optimize ndrolling nanreduce 675482176 | |
717572036 | https://github.com/pydata/xarray/issues/4325#issuecomment-717572036 | https://api.github.com/repos/pydata/xarray/issues/4325 | MDEyOklzc3VlQ29tbWVudDcxNzU3MjAzNg== | fujiisoup 6815844 | 2020-10-27T22:14:41Z | 2020-10-27T22:14:41Z | MEMBER | @mathause Oh, I missed this issue. Yes, this is implemented only for count.
Agreed. We need to clean this up. One possible option would be to drop support of bottleneck. This does not work for nd-rolling and if we implement the nd-nanreduce, the speed should be comparable with bottleneck. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Optimize ndrolling nanreduce 675482176 |
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