issue_comments: 122198334

This data as json

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/475#issuecomment-122198334 https://api.github.com/repos/pydata/xarray/issues/475 122198334 MDEyOklzc3VlQ29tbWVudDEyMjE5ODMzNA== 2443309 2015-07-17T06:54:37Z 2015-07-17T06:54:37Z MEMBER

Good point on the dask array business. From the dask docs:

Dask.array supports most of the NumPy slicing syntax. ... It does not currently support the following:

Slicing one dask.array with another x[x > 0] Slicing with lists in multiple axes x[[1, 2, 3], [3, 2, 1]]

Both of these are straightforward to add though. If you have a use case then raise an issue.

So, from browsing the closed dask issues, it seems like dask has similar support for multi-dimension slicing and indexing as xray. This throws a bit of a wrench in my plan for how I was going to implement isel_points as I had not fully considered the dask array complexities.

I'll have to put a bit more thought into this. Any suggestions on how to index the dask array without looping through individual points would be great.

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