issue_comments

Table actions

3 rows where issue = 276241764 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • max-sixty · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
554600952 https://github.com/pydata/xarray/issues/1739#issuecomment-554600952 https://api.github.com/repos/pydata/xarray/issues/1739 MDEyOklzc3VlQ29tbWVudDU1NDYwMDk1Mg== max-sixty 5635139 2019-11-16T03:48:19Z 2019-11-16T03:48:19Z MEMBER

OK great. We can meditate on it for a while, no great rush! Thanks for engaging.

 
{
    "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
554592920 https://github.com/pydata/xarray/issues/1739#issuecomment-554592920 https://api.github.com/repos/pydata/xarray/issues/1739 MDEyOklzc3VlQ29tbWVudDU1NDU5MjkyMA== max-sixty 5635139 2019-11-16T02:01:08Z 2019-11-16T02:01:08Z 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

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)?

 
{
    "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
554581481 https://github.com/pydata/xarray/issues/1739#issuecomment-554581481 https://api.github.com/repos/pydata/xarray/issues/1739 MDEyOklzc3VlQ29tbWVudDU1NDU4MTQ4MQ== max-sixty 5635139 2019-11-16T00:28:37Z 2019-11-16T00:28:37Z MEMBER

What do we think about attempting to enforce a dimension order throughout the dataset? That would solve these issues for free.

We already have some order in .dims & .sizes. Could we transpose all dimensions to that ordering after any operation?

(Maybe this doesn't need to be strictly enforced, but we'd at least set the expectation that dimensions could be reordered to that dimension order at any time)

Or are there uses to having different dimension order throughout a dataset?

```python In [45]: ds Out[45]: <xarray.Dataset> Dimensions: (lat: 25, lon: 53, time: 2920) Coordinates: * lat (lat) float32 75.0 72.5 70.0 67.5 65.0 ... 25.0 22.5 20.0 17.5 15.0 * lon (lon) float32 200.0 202.5 205.0 207.5 ... 322.5 325.0 327.5 330.0 * time (time) datetime64[ns] 2013-01-01 ... 2014-12-31T18:00:00 Data variables: air (time, lat, lon) float32 ... Attributes: Conventions: COARDS title: 4x daily NMC reanalysis (1948) description: Data is from NMC initialized reanalysis\n(4x/day). These a... platform: Model references: http://www.esrl.noaa.gov/psd/data/gridded/data.ncep.reanaly...

In [46]: ds.dims Out[46]: Frozen(SortedKeysDict({'lat': 25, 'time': 2920, 'lon': 53}))

In [47]: ds.sizes Out[47]: Frozen(SortedKeysDict({'lat': 25, 'time': 2920, 'lon': 53})) ```

 
{
    "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]);