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/1288#issuecomment-283127924,https://api.github.com/repos/pydata/xarray/issues/1288,283127924,MDEyOklzc3VlQ29tbWVudDI4MzEyNzkyNA==,1197350,2017-02-28T18:50:11Z,2017-02-28T18:50:11Z,MEMBER,And I'm fine with `integrate` if that is the consensus here.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,210704949
https://github.com/pydata/xarray/issues/1288#issuecomment-283062107,https://api.github.com/repos/pydata/xarray/issues/1288,283062107,MDEyOklzc3VlQ29tbWVudDI4MzA2MjEwNw==,1197350,2017-02-28T14:59:54Z,2017-02-28T14:59:54Z,MEMBER,"Having an xarray wrapper on `trapz` or `cumtrapz` would definitely be useful for many users. I weakly prefer not to use the name `integrate` and instead keep the standard scipy names because they make clear the numerical algorithm that is being applied. The issue is that certain types of gridded data (such as output from numerical models) should actually not be integrated with the trapezoidal rule but rather should use the native finite volume discretization for their computational grid. The goal of our hypothetical [pangeo vector calculus package](https://pangeo-data.github.io/packages/vector_calculus/) is to implement integrals and derivatives in such a context. A built-in xarray integration function would apply in cases where the data is assumed to be continuous, and where no auxiliary information about the grid (beyond the coordinates) is available.

I will also make the same comment I always make when such feature requests are raised: yes, it always seems desirable to add new features to xarray on a function-by-function basis. But where does it end? Why not implement the rest of the [scipy.ode](https://docs.scipy.org/doc/scipy-0.14.0/reference/integrate.integrate) module? And why stop there? As a community we need to develop a roadmap that clearly defines the scope of xarray. Once `apply` is stable, it might not be that hard to wrap a large fraction of the scipy library. But maybe that should live in a separate package.



","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,210704949