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/3147#issuecomment-1500985062,https://api.github.com/repos/pydata/xarray/issues/3147,1500985062,IC_kwDOAMm_X85Zdzbm,11092125,2023-04-08T21:58:27Z,2023-04-08T21:58:27Z,NONE,very much in need of this one to able satellite image filtering across blocks,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-1108212009,https://api.github.com/repos/pydata/xarray/issues/3147,1108212009,IC_kwDOAMm_X85CDfkp,3016805,2022-04-25T08:00:25Z,2022-04-25T08:00:25Z,NONE,"Indeed, this would be very useful in a great number of cases!","{""total_count"": 3, ""+1"": 3, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-1100938882,https://api.github.com/repos/pydata/xarray/issues/3147,1100938882,IC_kwDOAMm_X85Bnv6C,3019665,2022-04-17T19:44:03Z,2022-04-17T19:44:03Z,NONE,Would be good to keep this open,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-1100922143,https://api.github.com/repos/pydata/xarray/issues/3147,1100922143,IC_kwDOAMm_X85Bnr0f,26384082,2022-04-17T17:43:45Z,2022-04-17T17:43:45Z,NONE,"In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity
If this issue remains relevant, please comment here or remove the `stale` label; otherwise it will be marked as closed automatically
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-668263428,https://api.github.com/repos/pydata/xarray/issues/3147,668263428,MDEyOklzc3VlQ29tbWVudDY2ODI2MzQyOA==,3019665,2020-08-03T22:02:22Z,2020-08-03T22:02:22Z,NONE,"Yeah +1 for using `pad` instead. Had tried to get rid of `map_overlap`'s padding and use `da.pad` in Dask as well ( https://github.com/dask/dask/pull/5052 ), but haven't had time to get back to that.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-668256401,https://api.github.com/repos/pydata/xarray/issues/3147,668256401,MDEyOklzc3VlQ29tbWVudDY2ODI1NjQwMQ==,1312546,2020-08-03T21:42:42Z,2020-08-03T21:42:42Z,MEMBER,"Thanks for that link. I hope that map_overlap could use pad internally for
the external boundaries.
On Mon, Aug 3, 2020 at 3:22 PM Deepak Cherian
wrote:
> This issue about coordinate labels for boundaries exists with pad too:
> #3868
>
> Can map_overlap just use DataArray.pad and we can fix things there?
>
> Or perhaps we can expect users to add a call to pad before map_overlap?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> , or
> unsubscribe
>
> .
>
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-668223125,https://api.github.com/repos/pydata/xarray/issues/3147,668223125,MDEyOklzc3VlQ29tbWVudDY2ODIyMzEyNQ==,2448579,2020-08-03T20:22:23Z,2020-08-03T20:22:23Z,MEMBER,"This issue about coordinate labels for boundaries exists with pad too: https://github.com/pydata/xarray/issues/3868
Can `map_overlap` just use `DataArray.pad` and we can fix things there?
Or perhaps we can expect users to add a call to `pad` before `map_overlap`?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-668209121,https://api.github.com/repos/pydata/xarray/issues/3147,668209121,MDEyOklzc3VlQ29tbWVudDY2ODIwOTEyMQ==,1312546,2020-08-03T19:47:47Z,2020-08-03T19:47:57Z,MEMBER,"I'm thinking through a `map_overlap` API right now. In dask, map_overlap requires a few extra arguments
```
depth: int, tuple, dict or list
The number of elements that each block should share with its neighbors
If a tuple or dict then this can be different per axis.
If a list then each element of that list must be an int, tuple or dict
defining depth for the corresponding array in `args`.
Asymmetric depths may be specified using a dict value of (-/+) tuples.
Note that asymmetric depths are currently only supported when
``boundary`` is 'none'.
The default value is 0.
boundary: str, tuple, dict or list
How to handle the boundaries.
Values include 'reflect', 'periodic', 'nearest', 'none',
or any constant value like 0 or np.nan.
If a list then each element must be a str, tuple or dict defining the
boundary for the corresponding array in `args`.
The default value is 'reflect'.
```
In `dask.array` those must be dicts whose keys are the axis number. For xarray we would want to allow the dimension names there.
I'm not sure how to handle the DataArray labels for the boundary chunks (dask docs at https://docs.dask.org/en/latest/array-overlap.html#boundaries). For `reflect` / `periodic` I think things are OK, we perhaps just use the label associated with that value. I'm not sure what to do for constants.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-540845903,https://api.github.com/repos/pydata/xarray/issues/3147,540845903,MDEyOklzc3VlQ29tbWVudDU0MDg0NTkwMw==,2443309,2019-10-11T00:00:59Z,2019-10-11T00:00:59Z,MEMBER,`map_blocks` went in as of #3276. We'll leave this open for the future work implementing `map_overlap`.,"{""total_count"": 4, ""+1"": 3, ""-1"": 0, ""laugh"": 0, ""hooray"": 1, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-513044413,https://api.github.com/repos/pydata/xarray/issues/3147,513044413,MDEyOklzc3VlQ29tbWVudDUxMzA0NDQxMw==,3019665,2019-07-19T00:33:55Z,2019-07-19T00:42:03Z,NONE,"Another approach for the `split_by_chunks` implementation would be...
```python
def split_by_chunks(a):
for sl in da.core.slices_from_chunks(a.chunks):
yield (sl, a[sl])
```
While a little bit more cumbersome to write, this could be implemented with `.blocks` and may be a bit more performant.
```python
def split_by_chunks(a):
for i, sl in zip(np.ndindex(a.numblocks), da.core.slices_from_chunks(a.chunks)):
yield (sl, a.blocks[i])
```
If the slices are not strictly needed, this could be simplified a bit more.
```python
def split_by_chunks(a):
for i in np.ndindex(a.numblocks):
yield a.blocks[i]
```
Admittedly `slices_from_chunks` is an internal utility function. Though it is unlikely to change. We could consider exposing it as part of the API if that is useful.
We could consider other things like making `.blocks` iterable, which could make this more friendly as well. Raised issue ( https://github.com/dask/dask/issues/5117 ) on this point.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-513029753,https://api.github.com/repos/pydata/xarray/issues/3147,513029753,MDEyOklzc3VlQ29tbWVudDUxMzAyOTc1Mw==,3019665,2019-07-18T23:22:11Z,2019-07-18T23:22:11Z,NONE,That sounds somewhat similar to `.blocks` accessor in Dask Array. ( https://github.com/dask/dask/pull/3689 ) Maybe we should align on that as well?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896
https://github.com/pydata/xarray/issues/3147#issuecomment-513021156,https://api.github.com/repos/pydata/xarray/issues/3147,513021156,MDEyOklzc3VlQ29tbWVudDUxMzAyMTE1Ng==,2448579,2019-07-18T22:50:40Z,2019-07-18T22:50:40Z,MEMBER,+1. The `split_by_chunks` method in this comment (https://github.com/pydata/xarray/issues/1093#issuecomment-259213382) would also be useful for more general per-chunk manipulation.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,470024896