issues: 1076265104
This data as json
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1076265104 | PR_kwDOAMm_X84vpj53 | 6059 | Weighted quantile | 488992 | closed | 0 | 19 | 2021-12-10T01:11:36Z | 2022-03-27T20:36:22Z | 2022-03-27T20:36:22Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/6059 |
This is a follow-up to https://github.com/pydata/xarray/pull/5870/, which adds a weighted The question of how to precisely define the weighted quantile function is surprisingly complex, and this implementation offers a compromise in terms of simplicity and compatibility:
The interpolation question is so complex and confusing that entire articles have been written about it, as mentioned in the blog post above, in particular this one, which establishes the "nine types" taxoxomy, used, implicitly or not, by many software packages: https://doi.org/10.2307/2684934. The situation seems even more complex in the NumPy world, where many discussions and suggestions are aimed toward trying to improve the consistency of the API. The current non-weighted situation has the 9 options, as well as 4 extra legacy ones: https://github.com/numpy/numpy/blob/376ad691fe4df77e502108d279872f56b30376dc/numpy/lib/function_base.py#L4177-L4203 This PR cuts the Gordian knot by offering only one interpolation option, but.. given that its implementation is based on |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/6059/reactions", "total_count": 2, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 1, "rocket": 0, "eyes": 1 } |
13221727 | pull |