issue_comments

Table actions

4 rows where author_association = "MEMBER" and issue = 1548355645 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 3

issue 1

  • xr.DataSet.expand_dims axis option doesn't work · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1397312215 https://github.com/pydata/xarray/issues/7456#issuecomment-1397312215 https://api.github.com/repos/pydata/xarray/issues/7456 IC_kwDOAMm_X85TSUrX dcherian 2448579 2023-01-19T17:03:35Z 2023-01-19T17:03:35Z MEMBER

the documentation is very misleading

Updating the docstring would be a fairly easy and impactful PR if you're up for it!

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xr.DataSet.expand_dims axis option doesn't work 1548355645
1397025755 https://github.com/pydata/xarray/issues/7456#issuecomment-1397025755 https://api.github.com/repos/pydata/xarray/issues/7456 IC_kwDOAMm_X85TROvb dcherian 2448579 2023-01-19T14:00:49Z 2023-01-19T14:00:49Z MEMBER

I think it might be enough to describe this thoroughly with examples in the docstring., though I do like the solution of recommending transpose.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xr.DataSet.expand_dims axis option doesn't work 1548355645
1396923313 https://github.com/pydata/xarray/issues/7456#issuecomment-1396923313 https://api.github.com/repos/pydata/xarray/issues/7456 IC_kwDOAMm_X85TQ1ux keewis 14808389 2023-01-19T12:47:32Z 2023-01-19T12:48:06Z MEMBER

I wonder if we shouldn't recommend using expand_dims without axis plus a transpose afterwards if we care about dimension order? Most of xarray's functions work without making assumptions about the dimension order, and I don't think expand_dims should, either (though I might be missing something, of course)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xr.DataSet.expand_dims axis option doesn't work 1548355645
1396749591 https://github.com/pydata/xarray/issues/7456#issuecomment-1396749591 https://api.github.com/repos/pydata/xarray/issues/7456 IC_kwDOAMm_X85TQLUX kmuehlbauer 5821660 2023-01-19T10:26:56Z 2023-01-19T10:26:56Z MEMBER

@cmdupuis3 dimensions are not given in a particular order in the Dataset. There could be two DataArray's which have reversed dimensions for instance.

You would need to inspect the DataArray's:

python da = xr.DataArray([[1,2,3],[4,5,6],[7,8,9]], coords={'a':[1,2,3], 'b':[1,2,3]}) ds = xr.Dataset({'da':da}) ds0 = ds.expand_dims('yomama', axis=0) print(ds0.dims) print(ds0.da.dims) ds1 = ds.expand_dims('yomama', axis=1) print(ds1.dims) print(ds1.da.dims) ds2 = ds.expand_dims('yomama', axis=2) print(ds2.dims) print(ds2.da.dims) python Frozen({'a': 3, 'b': 3, 'yomama': 1}) ('yomama', 'a', 'b') Frozen({'a': 3, 'b': 3, 'yomama': 1}) ('a', 'yomama', 'b') Frozen({'a': 3, 'b': 3, 'yomama': 1}) ('a', 'b', 'yomama')

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xr.DataSet.expand_dims axis option doesn't work 1548355645

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