{"action":"created","issue":{"url":"https://api.github.com/repos/blaze/dask/issues/702","labels_url":"https://api.github.com/repos/blaze/dask/issues/702/labels{/name}","comments_url":"https://api.github.com/repos/blaze/dask/issues/702/comments","events_url":"https://api.github.com/repos/blaze/dask/issues/702/events","html_url":"https://github.com/blaze/dask/issues/702","id":106185177,"number":702,"title":"atop with multiple output arguments","user":{"login":"shoyer","id":1217238,"avatar_url":"https://avatars.githubusercontent.com/u/1217238?v=3","gravatar_id":"","url":"https://api.github.com/users/shoyer","html_url":"https://github.com/shoyer","followers_url":"https://api.github.com/users/shoyer/followers","following_url":"https://api.github.com/users/shoyer/following{/other_user}","gists_url":"https://api.github.com/users/shoyer/gists{/gist_id}","starred_url":"https://api.github.com/users/shoyer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shoyer/subscriptions","organizations_url":"https://api.github.com/users/shoyer/orgs","repos_url":"https://api.github.com/users/shoyer/repos","events_url":"https://api.github.com/users/shoyer/events{/privacy}","received_events_url":"https://api.github.com/users/shoyer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-09-12T21:11:15Z","updated_at":"2015-09-12T21:57:45Z","closed_at":null,"body":"Yesterday, we (@mrocklin, @clarkfitzg and myself) discussed writing some sort of user facing API for `atop` for xray that makes use of xray's metadata to automatically generate complex `atop` calls by inspecting the result of applying the function to a single block.\r\n\r\nTo make this work generically as a function that transforms `xray.Dataset` objects, which can be containers of multiple dask arrays, we need a version of `atop` where the applied function `func` can have multiple output arguments."},"comment":{"url":"https://api.github.com/repos/blaze/dask/issues/comments/139822526","html_url":"https://github.com/blaze/dask/issues/702#issuecomment-139822526","issue_url":"https://api.github.com/repos/blaze/dask/issues/702","id":139822526,"user":{"login":"shoyer","id":1217238,"avatar_url":"https://avatars.githubusercontent.com/u/1217238?v=3","gravatar_id":"","url":"https://api.github.com/users/shoyer","html_url":"https://github.com/shoyer","followers_url":"https://api.github.com/users/shoyer/followers","following_url":"https://api.github.com/users/shoyer/following{/other_user}","gists_url":"https://api.github.com/users/shoyer/gists{/gist_id}","starred_url":"https://api.github.com/users/shoyer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shoyer/subscriptions","organizations_url":"https://api.github.com/users/shoyer/orgs","repos_url":"https://api.github.com/users/shoyer/repos","events_url":"https://api.github.com/users/shoyer/events{/privacy}","received_events_url":"https://api.github.com/users/shoyer/received_events","type":"User","site_admin":false},"created_at":"2015-09-12T21:57:45Z","updated_at":"2015-09-12T21:57:45Z","body":"I'm OK with chunks along a dimension either preserving their shape or being collapsed entirely.\r\n\r\nWhat I would like, though, is the ability to create new, unchunked, dimensions. I suspect that we could accommodate this by adjusting the `numblocks` argument to `top`, e.g., instead of this:\r\n\r\n    >>> top(add, 'z', 'ij', 'x', 'ij', 'y', 'ij', numblocks={'x': (2, 2),\r\n    ...                                                      'y': (2, 2)})  # doctest: +SKIP\r\n\r\nwe should specify blocks like this:\r\n\r\n    >>> top(add, 'z', 'ij', 'x', 'ij', 'y', 'ij', dims={'i': 2, 'j': 2})\r\n\r\nNew dimensions would be required to have a single block, or alternatively, could be interpreted as indicating a function that yields multiple chunks, e.g.,\r\n\r\n    def output_many(x):\r\n        for j in range(10):\r\n            yield x + j\r\n\r\n     top(output_many, 'z', 'ij', 'x', 'i', dims={'i': 5, 'j': 10})\r\n\r\nI don't actually have an any use cases in mind for yielding multiple chunks along new dimensions, though."}}