home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

8 rows where issue = 317421267 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 5

  • shoyer 2
  • crusaderky 2
  • fujiisoup 2
  • rabernat 1
  • fmaussion 1

issue 1

  • New feature: interp1d · 8 ✖

author_association 1

  • MEMBER 8
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
386906920 https://github.com/pydata/xarray/issues/2079#issuecomment-386906920 https://api.github.com/repos/pydata/xarray/issues/2079 MDEyOklzc3VlQ29tbWVudDM4NjkwNjkyMA== crusaderky 6213168 2018-05-06T19:30:30Z 2018-05-06T19:30:30Z MEMBER

As I was dissatisfied with the prototype, I scrapped it and rewrote it mocking the splrep/splev API. However my functions don't wrap around scipy.interpolate.splrep/splev, as those don't accept an n-dimensional y, but instead they wrap around scipy.interpolate.make_interp_spline and scipy.interpolate.BSpline (which is what scipy.interpolate.interp1d does too). Compared to the prototype above:

  • lost support for Akima, PCHIP, and the non-spline options of interp1d
  • MUCH more memory-efficient than before, particularly on distributed
  • no more hacks - splrep produces a plain Dataset, which can be stored on NetCDF, sliced, etc. etc.
  • gained ability to have chunks on x_new

I built a production-quality version (inclusive of documentation, unit tests, and all the trimmings) at https://github.com/crusaderky/xarray_extras. Happy to discuss moving it to somebody else's module.

You still can't have a chunked x. It is possible to implement it with dask.array.ghost.ghost, although it would be mutually exclusive with a chunked x_new - contributions are welcome.

Closing this ticket as I agree this is beyond the scope of the core xarray package.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  New feature: interp1d 317421267
384715582 https://github.com/pydata/xarray/issues/2079#issuecomment-384715582 https://api.github.com/repos/pydata/xarray/issues/2079 MDEyOklzc3VlQ29tbWVudDM4NDcxNTU4Mg== shoyer 1217238 2018-04-26T17:02:19Z 2018-04-26T17:02:19Z MEMBER

This functionality sounds similar to reindex. Is it confusing to add this to reindex with an additional method such as method='linear'?

I think this would be a little confusing because then reindex in xarray would work differently from reindex in pandas.

Also, interpolate is a more descriptive name than reindex, at least for scientists. I would rather read array.interpolate_at(x=points) than array.reindex_like(x=points, method='linear').

{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  New feature: interp1d 317421267
384711274 https://github.com/pydata/xarray/issues/2079#issuecomment-384711274 https://api.github.com/repos/pydata/xarray/issues/2079 MDEyOklzc3VlQ29tbWVudDM4NDcxMTI3NA== fmaussion 10050469 2018-04-26T16:48:31Z 2018-04-26T16:48:31Z MEMBER

I am very much in favor of an xarray built-in interpolate_at method. Interpolating/regridding is domain agnostic and would be extremely useful to many downstream packages (salem does some regridding but it all happens on memory and uses scipy's RegularGridInterpolator under the hood). I would love to have an xarray func for this...

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  New feature: interp1d 317421267
384366752 https://github.com/pydata/xarray/issues/2079#issuecomment-384366752 https://api.github.com/repos/pydata/xarray/issues/2079 MDEyOklzc3VlQ29tbWVudDM4NDM2Njc1Mg== crusaderky 6213168 2018-04-25T17:22:33Z 2018-04-25T17:22:33Z MEMBER

For my use case slrep caching is critical, as I need to interpolate 20-something curves roughly 4000 times on different points. Changing the application to gather all points from downstream and do one big interpolation would not be feasible as it would kill off my RAM and be very hostile to a distributed environment.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  New feature: interp1d 317421267
384291663 https://github.com/pydata/xarray/issues/2079#issuecomment-384291663 https://api.github.com/repos/pydata/xarray/issues/2079 MDEyOklzc3VlQ29tbWVudDM4NDI5MTY2Mw== rabernat 1197350 2018-04-25T13:44:39Z 2018-04-25T13:44:39Z MEMBER

Regarding interpolation, this is one of the most common needs of users. I would support adding some sort of basic interpolation directly within xarray. I would eventually like to see multilinear n-dimensional interpolation supported.

I personally think that it would be nicer if we merge these similar packages and make them more complete.

xrft is focused quite narrowly on spectral analysis. It is very useful for our research group. But we haven't put much effort into making it widely accessible or comprehensive.

I agree that in principle it would be good to merge efforts. However, we say this often about this type of project, but in practice I'm not sure we have the time to really accomplish it. It would take significant developer effort. xr-scipy seems the most mature and well designed of the three packages, so that should probably be the one we focus efforts on if we go that route.

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  New feature: interp1d 317421267
384141407 https://github.com/pydata/xarray/issues/2079#issuecomment-384141407 https://api.github.com/repos/pydata/xarray/issues/2079 MDEyOklzc3VlQ29tbWVudDM4NDE0MTQwNw== fujiisoup 6815844 2018-04-25T02:27:38Z 2018-04-25T02:27:38Z MEMBER

If it were not for caching the grid setup, then this would make sense as a built-in xarray method interpolate_at (to complement interpolate_na).

This functionality sounds similar to reindex. Is it confusing to add this to reindex with an additional method such as method='linear'?

@fujiisoup also note @rabernat's xrft package, which has some overlap with your xr-scipy package.

This looks nice. I personally think that it would be nicer if we merge these similar packages and make them more complete. But yes, we can start listing these packages on a doc page first.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  New feature: interp1d 317421267
384138278 https://github.com/pydata/xarray/issues/2079#issuecomment-384138278 https://api.github.com/repos/pydata/xarray/issues/2079 MDEyOklzc3VlQ29tbWVudDM4NDEzODI3OA== shoyer 1217238 2018-04-25T02:06:29Z 2018-04-25T02:06:29Z MEMBER

If it were not for caching the grid setup, then this would make sense as a built-in xarray method interpolate_at (to complement interpolate_na).

With caching, this feels a little bit beyond the standard xarray data model, but well suited for a companion package. It would be great to start listing these on a doc page, so users can easily find them!

@fujiisoup also note @rabernat's xrft package, which has some overlap with your xr-scipy package.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  New feature: interp1d 317421267
384113386 https://github.com/pydata/xarray/issues/2079#issuecomment-384113386 https://api.github.com/repos/pydata/xarray/issues/2079 MDEyOklzc3VlQ29tbWVudDM4NDExMzM4Ng== fujiisoup 6815844 2018-04-24T23:36:07Z 2018-04-24T23:36:07Z MEMBER

I think Interpolation (and scipy integration) is one of a good extensions of xarray ecosystem.

We discussed previously about contribute package/module in #1850 #1288 . It sounds a good idea to me to start from contrib.scipy module.

I notice that different people have developed almost the same package in parallel, https://github.com/lamorton/SciPyXarray https://github.com/fujiisoup/xr-scipy and maybe more.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  New feature: interp1d 317421267

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

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]);
Powered by Datasette · Queries took 12.74ms · About: xarray-datasette