issue_comments
4 rows where author_association = "MEMBER" and issue = 484622545 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- interp and reindex should work for 1d -> nd indexing · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
582987147 | https://github.com/pydata/xarray/issues/3252#issuecomment-582987147 | https://api.github.com/repos/pydata/xarray/issues/3252 | MDEyOklzc3VlQ29tbWVudDU4Mjk4NzE0Nw== | shoyer 1217238 | 2020-02-06T16:26:11Z | 2020-02-06T16:26:11Z | MEMBER | I recently wrote a version of scipy.ndimage.map_coordinates for JAX in pure NumPt that I think could be straightforwardly ported into xarray. On Thu, Feb 6, 2020 at 7:00 AM David Huard notifications@github.com wrote:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interp and reindex should work for 1d -> nd indexing 484622545 | |
524572529 | https://github.com/pydata/xarray/issues/3252#issuecomment-524572529 | https://api.github.com/repos/pydata/xarray/issues/3252 | MDEyOklzc3VlQ29tbWVudDUyNDU3MjUyOQ== | shoyer 1217238 | 2019-08-24T18:45:53Z | 2019-08-24T18:45:53Z | MEMBER | We could probably use this our own version for all linear and nearest neighbor interpolation. Then we won’t need scipy installed for that. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interp and reindex should work for 1d -> nd indexing 484622545 | |
524457928 | https://github.com/pydata/xarray/issues/3252#issuecomment-524457928 | https://api.github.com/repos/pydata/xarray/issues/3252 | MDEyOklzc3VlQ29tbWVudDUyNDQ1NzkyOA== | shoyer 1217238 | 2019-08-23T20:50:29Z | 2019-08-23T20:50:29Z | MEMBER | Linear interpolation for 1d -> nd is just a matter of averaging two indexing selections. If we leverage xarray's vectorized indexing operations to do the hard work, it should work automatically for dask arrays, sparse arrays and xarray's internal backend array types, all with any number of dimensions. On Fri, Aug 23, 2019 at 2:17 PM Noah D Brenowitz notifications@github.com wrote:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interp and reindex should work for 1d -> nd indexing 484622545 | |
524439002 | https://github.com/pydata/xarray/issues/3252#issuecomment-524439002 | https://api.github.com/repos/pydata/xarray/issues/3252 | MDEyOklzc3VlQ29tbWVudDUyNDQzOTAwMg== | shoyer 1217238 | 2019-08-23T19:43:21Z | 2019-08-23T19:43:21Z | MEMBER | We could implement linear interpolation just as |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interp and reindex should work for 1d -> nd indexing 484622545 |
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 1