home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 42633675

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/116#issuecomment-42633675 https://api.github.com/repos/pydata/xarray/issues/116 42633675 MDEyOklzc3VlQ29tbWVudDQyNjMzNjc1 1217238 2014-05-09T05:01:38Z 2014-05-09T05:02:16Z MEMBER

As I think more about this one, I'm questioning the value of allowing for unnamed dimensions, as opposed to simply defaulting to dimension names like "dim_0", "dim_1", etc.

In particular, unnamed dimensions are not very useful on object which use indices for alignment. To do sensible numpy like broadcasting, you need to be able to insert size 1 dimensions. But since we always have tick labels, we can't automatically expand those size 1 dimensions to the size of the dimension in the other array.

I suppose we could also make tick labels optional, which would make reshape operations or np.newaxis sensible. But I think I would rather still default to np.arange(size) like pandas.

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