home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 525384446

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/pull/3258#issuecomment-525384446 https://api.github.com/repos/pydata/xarray/issues/3258 525384446 MDEyOklzc3VlQ29tbWVudDUyNTM4NDQ0Ng== 1217238 2019-08-27T16:40:32Z 2019-08-27T16:40:32Z MEMBER
  • could we call it just "map"? It makes sense as this thing would be very useful for non-dask based arrays too. Working routinely with scipy (chiefly with scipy.stats transforms), I tire a lot of writing very verbose xarray.apply_ufunc calls.

I agree that apply_ufunc is overly verbose. See https://github.com/pydata/xarray/issues/1074 and https://github.com/pydata/xarray/issues/1618 (and issues linked therein) for discussion about alternative APIs.

I still think this particular set of functionality should be called map_blocks, because it works by applying functions over each block, very similar to dask's map_blocks.

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  484752930
Powered by Datasette · Queries took 80.824ms · About: xarray-datasette