issue_comments: 241232491
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/979#issuecomment-241232491 | https://api.github.com/repos/pydata/xarray/issues/979 | 241232491 | MDEyOklzc3VlQ29tbWVudDI0MTIzMjQ5MQ== | 1217238 | 2016-08-21T00:55:11Z | 2016-08-21T00:55:11Z | MEMBER | I agree that it would make sense for As you can see, the automatic rechunking algorithm that dask.array currently uses is super simple: it only reconciles chunks when one array is unchunked. I'm certainly open to more sophisticated options for automatic rechunking (see https://github.com/dask/dask/issues/111), but either way I'd prefer to keep as much of this logic on the dask side as possible. Ideally, we'd simply call |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
172291585 |