issue_comments: 702363119
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/issues/4474#issuecomment-702363119 | https://api.github.com/repos/pydata/xarray/issues/4474 | 702363119 | MDEyOklzc3VlQ29tbWVudDcwMjM2MzExOQ== | 5635139 | 2020-10-01T19:55:11Z | 2020-10-01T19:55:11Z | MEMBER | Thanks @heerad . Looks like we're doing it with overlaps rather than any rolling-specific algo. Agree that approach won't work with exp. OTOH your suggestion could be generalized to improve performance in all rolling operations, depending on the relative costs of sending the underlying overlapping data vs. sending only the edges of the numerator / denominator and doing another pass. If anyone has experience with similar operations, feel free to offer suggestions. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
712052219 |