issue_comments
14 rows where author_association = "MEMBER", issue = 95114700 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- API design for pointwise indexing · 14 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
633185598 | https://github.com/pydata/xarray/issues/475#issuecomment-633185598 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDYzMzE4NTU5OA== | shoyer 1217238 | 2020-05-24T06:18:00Z | 2020-05-24T06:21:03Z | MEMBER | @JimmyGao0204 I moved your comment to a new issue: https://github.com/pydata/xarray/issues/4090 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
355085272 | https://github.com/pydata/xarray/issues/475#issuecomment-355085272 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDM1NTA4NTI3Mg== | shoyer 1217238 | 2018-01-03T18:16:29Z | 2018-01-03T18:16:29Z | MEMBER | @jhamman @stefanomattia can you share a link to this blog post? :) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
342577675 | https://github.com/pydata/xarray/issues/475#issuecomment-342577675 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDM0MjU3NzY3NQ== | shoyer 1217238 | 2017-11-07T18:31:30Z | 2017-11-07T18:31:30Z | MEMBER | Yes, a documentation example would be greatly appreciated. We have been making progress in this direction (especially with the new vectorised indexing support) but it has been slow going to do it right. On Tue, Nov 7, 2017 at 10:29 AM Benjamin Root notifications@github.com wrote:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
241821366 | https://github.com/pydata/xarray/issues/475#issuecomment-241821366 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDI0MTgyMTM2Ng== | shoyer 1217238 | 2016-08-23T18:05:09Z | 2017-02-09T23:21:14Z | MEMBER | A few recent developments relevant to this issue:
- #974 discusses how we could add multi-dimensional indexing with broadcasting. This would subsume the need for separate methods like So I'm now thinking an API more like this: ```
For building a tree with lat/lon remapped to spherical coordinates, we should write a method that converts lat and lon arrays into a tuple of x, y, z arrays (e.g., using |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
256207074 | https://github.com/pydata/xarray/issues/475#issuecomment-256207074 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDI1NjIwNzA3NA== | shoyer 1217238 | 2016-10-25T23:19:03Z | 2016-10-25T23:19:03Z | MEMBER | @burnpanck Nevermind, you are correct! I misread your comment. This cannot be done currently. You certainly could try to put this into |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
256201020 | https://github.com/pydata/xarray/issues/475#issuecomment-256201020 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDI1NjIwMTAyMA== | shoyer 1217238 | 2016-10-25T22:49:14Z | 2016-10-25T22:49:14Z | MEMBER | @burnpanck I don't think you need to do the flattening/multi-index bit. I believe At this point we're really just talking about design refinements (I'll rename the topic). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
126851732 | https://github.com/pydata/xarray/issues/475#issuecomment-126851732 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDEyNjg1MTczMg== | shoyer 1217238 | 2015-08-01T02:29:37Z | 2015-08-01T02:29:37Z | MEMBER | PR #507 implements the my suggested 1d version of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
125468579 | https://github.com/pydata/xarray/issues/475#issuecomment-125468579 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDEyNTQ2ODU3OQ== | shoyer 1217238 | 2015-07-28T06:43:26Z | 2015-07-28T06:43:26Z | MEMBER | I started playing around with making an array wrapper for KDTree this evening: https://gist.github.com/shoyer/ae30a1200f749c84b4c4 I think it has most of the necessary indexing machinery and you can put it in an xray.Dataset like an array. You could easily imagine hooking in a |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
125349079 | https://github.com/pydata/xarray/issues/475#issuecomment-125349079 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDEyNTM0OTA3OQ== | shoyer 1217238 | 2015-07-27T21:34:42Z | 2015-07-27T21:34:42Z | MEMBER | I would start with the easiest case -- lookups of 1d orthogonal arrays, e.g., For 2D lookups, we need a KDTree. Here are some API ideas, just tossing things around... ```
perhaps set_ndindex is a better name?
result = ds.sel_points(latitude=other.latitude, longitude=other.longitude, method='nearest') ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
122440826 | https://github.com/pydata/xarray/issues/475#issuecomment-122440826 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDEyMjQ0MDgyNg== | shoyer 1217238 | 2015-07-17T23:05:59Z | 2015-07-17T23:05:59Z | MEMBER |
For now, I actually think selecting individual points and then concatenating the resulting arrays together would be a reasonable start. Yes, it's kind of slow, but once you have a first draft put together that way with the right API we can optimize later. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
122001943 | https://github.com/pydata/xarray/issues/475#issuecomment-122001943 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDEyMjAwMTk0Mw== | shoyer 1217238 | 2015-07-16T15:59:18Z | 2015-07-16T15:59:18Z | MEMBER | @jhamman it would be great if you could put together a PR for As for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
121808018 | https://github.com/pydata/xarray/issues/475#issuecomment-121808018 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDEyMTgwODAxOA== | shoyer 1217238 | 2015-07-16T02:47:30Z | 2015-07-16T02:47:30Z | MEMBER | I agree that regridding and resample would be very nice, and pyresample looks like a decent option. I have no immediate plans to implement these features but contributions would be very welcome. For n-dimensional indexing, kdtree seems sensible, especially if we can cache it on the coordinates. We probably want an explicit API for methods that add new coordinates -- something like |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
121703276 | https://github.com/pydata/xarray/issues/475#issuecomment-121703276 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDEyMTcwMzI3Ng== | shoyer 1217238 | 2015-07-15T18:22:03Z | 2015-07-15T18:22:03Z | MEMBER |
Yes, this is a reasonable choice for the case of 1d indexers.
This is also a good idea, though I would probably call the parameter
Indeed. As a start, we should be able to do nearest neighbor lookups with a tolerance soon -- I have a pandas PR that should add some of that basic functionality (https://github.com/pydata/pandas/pull/10411). In the long term, it would be useful to have some sort of representation of grid cells in the index itself, possibly something similar to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
121679580 | https://github.com/pydata/xarray/issues/475#issuecomment-121679580 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDEyMTY3OTU4MA== | shoyer 1217238 | 2015-07-15T16:58:36Z | 2015-07-15T16:58:36Z | MEMBER | So, the good news is that once we figure out the API for pointwise indexing, I think the nearest-neighbor part could be as simple as supplying The challenge is that we want to go from an DataArray that looks like this: ``` In [4]: arr = xray.DataArray([[1, 2], [3, 4]], dims=['x', 'y']) In [5]: arr Out[5]: <xray.DataArray (x: 2, y: 2)> array([[1, 2], [3, 4]]) Coordinates: * x (x) int64 0 1 * y (y) int64 0 1 ``` To one that looks like that:
Somehow, we need to figure out the name for the new dimension ( My thought would be to have methods If you don't already have 1D xray objects, I suppose we could also allow |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 |
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