issue_comments
3 rows where issue = 210704949 and user = 1386642 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Add trapz to DataArray for mathematical integration · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
359534363 | https://github.com/pydata/xarray/issues/1288#issuecomment-359534363 | https://api.github.com/repos/pydata/xarray/issues/1288 | MDEyOklzc3VlQ29tbWVudDM1OTUzNDM2Mw== | nbren12 1386642 | 2018-01-22T19:19:25Z | 2018-01-22T19:19:25Z | CONTRIBUTOR | I would also be very interested in seeing your codes @lamorton. Overall, I think the xarray community could really benefit from some kind of centralized |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add trapz to DataArray for mathematical integration 210704949 | |
287768014 | https://github.com/pydata/xarray/issues/1288#issuecomment-287768014 | https://api.github.com/repos/pydata/xarray/issues/1288 | MDEyOklzc3VlQ29tbWVudDI4Nzc2ODAxNA== | nbren12 1386642 | 2017-03-20T14:03:10Z | 2017-03-20T14:03:10Z | CONTRIBUTOR | I usually agree that using too many (or any) switches within functions is not ideal. However, I think this is more important for low level or internal routines. For user facing interfaces, I think it is okay. After all, many numpy and scipy functions have convenient switches that control the return values. By the way, the cumtrapz implementation I pasted above matches the scipy version when initial=0, which I also think would be a more sane default for integration. As far as implementation is concerned. Is there any performance downside to using xarrays shift operators versus delving deeper into dask with map_blocks, etc? I looked into using dasks cumreduction function, but am not sure it is possible to implement the trapezoid method in that way without changing dask. On Mon, Mar 20, 2017 at 8:48 AM Fabien Maussion notifications@github.com wrote:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add trapz to DataArray for mathematical integration 210704949 | |
287673906 | https://github.com/pydata/xarray/issues/1288#issuecomment-287673906 | https://api.github.com/repos/pydata/xarray/issues/1288 | MDEyOklzc3VlQ29tbWVudDI4NzY3MzkwNg== | nbren12 1386642 | 2017-03-20T03:45:18Z | 2017-03-20T03:45:18Z | CONTRIBUTOR | I would also like to see an ```python def cumtrapz(A, dim): """Cumulative Simpson's rule (aka Tai's method)
``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add trapz to DataArray for mathematical integration 210704949 |
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