issue_comments
7 rows where author_association = "MEMBER" and issue = 38849807 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- interpolate/sample array at point · 7 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
454164740 | https://github.com/pydata/xarray/issues/191#issuecomment-454164740 | https://api.github.com/repos/pydata/xarray/issues/191 | MDEyOklzc3VlQ29tbWVudDQ1NDE2NDc0MA== | fujiisoup 6815844 | 2019-01-14T21:17:37Z | 2019-01-14T21:17:37Z | MEMBER | closed via #2104 |
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 1, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interpolate/sample array at point 38849807 | |
454163673 | https://github.com/pydata/xarray/issues/191#issuecomment-454163673 | https://api.github.com/repos/pydata/xarray/issues/191 | MDEyOklzc3VlQ29tbWVudDQ1NDE2MzY3Mw== | max-sixty 5635139 | 2019-01-14T21:14:15Z | 2019-01-14T21:14:15Z | MEMBER | @fujiisoup could we close this given your recent work |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interpolate/sample array at point 38849807 | |
204440000 | https://github.com/pydata/xarray/issues/191#issuecomment-204440000 | https://api.github.com/repos/pydata/xarray/issues/191 | MDEyOklzc3VlQ29tbWVudDIwNDQ0MDAwMA== | shoyer 1217238 | 2016-04-01T15:35:14Z | 2016-04-01T15:35:14Z | MEMBER | Yes, this like looks useful to me! On Fri, Apr 1, 2016 at 7:32 AM, Stefan Pfenninger notifications@github.com wrote:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interpolate/sample array at point 38849807 | |
150733056 | https://github.com/pydata/xarray/issues/191#issuecomment-150733056 | https://api.github.com/repos/pydata/xarray/issues/191 | MDEyOklzc3VlQ29tbWVudDE1MDczMzA1Ng== | shoyer 1217238 | 2015-10-24T01:31:32Z | 2015-10-24T01:31:32Z | MEMBER | @saulomeirelles I don't have any progress to share on this issue. If this issue is important to you, contributions would be gratefully accepted! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interpolate/sample array at point 38849807 | |
50437246 | https://github.com/pydata/xarray/issues/191#issuecomment-50437246 | https://api.github.com/repos/pydata/xarray/issues/191 | MDEyOklzc3VlQ29tbWVudDUwNDM3MjQ2 | shoyer 1217238 | 2014-07-29T05:56:26Z | 2014-07-29T05:57:36Z | MEMBER | Actually, I'm thinking now that we could probably (theoretically) fit all interpolation strategies into a single That said... perhaps its better to stick with a simpler function for now and we can figure out the bigger picture later. Looking at all the scipy functions, there are a lot of hypothetical options and I'm not sure which we'd want to keep in the final method. Also, kitchen sink type functions (e.g., |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interpolate/sample array at point 38849807 | |
50425930 | https://github.com/pydata/xarray/issues/191#issuecomment-50425930 | https://api.github.com/repos/pydata/xarray/issues/191 | MDEyOklzc3VlQ29tbWVudDUwNDI1OTMw | shoyer 1217238 | 2014-07-29T01:56:53Z | 2014-07-29T05:48:55Z | MEMBER | So I would definitely still wrap the scipy functions for any interpolation routines for xray. It's not worth rewriting any of them twice! Scipy is an optional dependency for xray, but it would be fine to require it for the interpolation routines. Yes, there do seems to be a few different interpolation routines in scipy. Naming the function you're thinking of something like In xray, we have DataArray objects (corresponding to a particular variable in a netCDF file along with its coordinates) as well as Datasets (corresponding to entire netCDFs). I think it makes a bit more sense to interpolate individual variables, so I guess you would want this function to have a signature something like the following: ``` Parameters source : DataArray Gridded source data. destination : ndarray or dict-like (e.g., xray.Dataset or pandas.DataFrame) Array of points of points to sample at (n_obs * n_dim) or mapping from dimension names to coordinate values. order : int, optional mode : {'constant', 'nearest'}, optional cval : scalar, optional Maybe defaulting to NaN instead of 0? Returnsinterpolated : DataArray Data array with interpolated values. Coordinates and dimensions are copied from points. ``` You don't need to necessarily handle all the edge cases of possible input to The DataArray constructor isn't in the currently released version of xray but it will be a major feature of the next release (hopefully to be released in a week or two) and it might be worth using here. It should be clearly documented in the docstring of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interpolate/sample array at point 38849807 | |
50296450 | https://github.com/pydata/xarray/issues/191#issuecomment-50296450 | https://api.github.com/repos/pydata/xarray/issues/191 | MDEyOklzc3VlQ29tbWVudDUwMjk2NDUw | shoyer 1217238 | 2014-07-28T03:07:04Z | 2014-07-28T03:07:04Z | MEMBER | Hi Richard, Your question is actually very timely. We don't have any routines yet to do interpolation, although one of my colleagues (not sure if he's on GitHub) was looking into 1-dimensional interpolation last week. A contribution to add interpolation to xray would certainly be very welcome! I would not recommend wrapping the pandas routines -- they just use their own wrapper over scipy and only interpolate in 1D. They also have somewhat unusual API -- they support interpolation only to fill in missing values (marked with Scipy has a wide variety of interpolation options, most of which I have not used. I'm guessing you're most immediately interested in doing something with map_coordinates? What were you thinking for the function signature? As for where to put it, we have two options:
1. Add a method |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
interpolate/sample array at point 38849807 |
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