home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

5 rows where issue = 276241764 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
554594809 https://github.com/pydata/xarray/issues/1739#issuecomment-554594809 https://api.github.com/repos/pydata/xarray/issues/1739 MDEyOklzc3VlQ29tbWVudDU1NDU5NDgwOQ== shoyer 1217238 2019-11-16T02:21:44Z 2019-11-16T02:21:44Z MEMBER

we would either have to raise an error or automatically transpose the second variable. Neither option sounds great to me.

Agree, I was thinking we'd transpose the second one, but fair if you think too invasive

Maybe this would be fine. We already do automatic alignment, and this is really not that much different.

It would be a breaking change, though, so we would need to roll it out slowly.

Perhaps this could be relaxed now that Python's dict always preserves the order in which items are added.

Ah OK. If we relaxed that, what would the order be? Just the order they were initially added, and so at least consistent through time (though not necessarily with the variables)?

Yes, that's right.

One potential concern is that this would expose a detail of xarray's data model that would not be easy for users to control. I can imagine that we might have internal xarray methods that inadvertently change dimension order.

So maybe this would make sense only if we also do your other suggested change (enforcing a consistent dimension order throughout a Dataset).

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Utility to restore original dimension order after apply_ufunc 276241764
554585004 https://github.com/pydata/xarray/issues/1739#issuecomment-554585004 https://api.github.com/repos/pydata/xarray/issues/1739 MDEyOklzc3VlQ29tbWVudDU1NDU4NTAwNA== shoyer 1217238 2019-11-16T00:50:57Z 2019-11-16T00:50:57Z MEMBER

Consistent dimension ordering is usually a best practice, but I'm not sure we want to enforce it. If a user explicitly supplies two variables, with dimensions ('x', 'y') and ('y', 'x'), respectively, we would either have to raise an error or automatically transpose the second variable. Neither option sounds great to me.

As for the current order in ds.dims, right now we use sorted order. Mostly this is because I didn't want to need to use an OrderedDict for keeping track of dimensions on datasets, and until recently Python dict order was entirely arbitrary. Perhaps this could be relaxed now that Python's dict always preserves the order in which items are added.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Utility to restore original dimension order after apply_ufunc 276241764
350151394 https://github.com/pydata/xarray/issues/1739#issuecomment-350151394 https://api.github.com/repos/pydata/xarray/issues/1739 MDEyOklzc3VlQ29tbWVudDM1MDE1MTM5NA== shoyer 1217238 2017-12-08T02:06:59Z 2017-12-08T02:06:59Z MEMBER

What if we just supplied an output_dims kwarg to apply_ufunc or apply_raw?

We could do that, but how to do we handle specifying output dimensions for a Dataset function? Maybe use a dict?

This is part of why a helper function starts to make sense to me.

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Utility to restore original dimension order after apply_ufunc 276241764
347178210 https://github.com/pydata/xarray/issues/1739#issuecomment-347178210 https://api.github.com/repos/pydata/xarray/issues/1739 MDEyOklzc3VlQ29tbWVudDM0NzE3ODIxMA== shoyer 1217238 2017-11-27T13:15:42Z 2017-11-27T13:15:42Z MEMBER

I started trying to implement this in apply_ufunc and then realized why I hadn't done so before: it's really not clear how to match up input/output arguments if there are more than one of each. We could do something special for there first input/output but that could be more confusing than helpful.

This is probably better reserved for the simpler apply_raw(https://github.com/pydata/xarray/issues/1618).

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Utility to restore original dimension order after apply_ufunc 276241764
346746989 https://github.com/pydata/xarray/issues/1739#issuecomment-346746989 https://api.github.com/repos/pydata/xarray/issues/1739 MDEyOklzc3VlQ29tbWVudDM0Njc0Njk4OQ== shoyer 1217238 2017-11-24T05:39:22Z 2017-11-24T05:39:22Z MEMBER

I wonder if it would make sense to simply change the behavior of apply_ufunc so existing dimensions always get restored to their original location, and only new dimensions remain at the end. It seems like this is almost always desirable.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Utility to restore original dimension order after apply_ufunc 276241764

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);
Powered by Datasette · Queries took 4294.846ms · About: xarray-datasette