issue_comments

Table actions

1 row where issue = 1452123685 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • keewis · 1 ✖

issue 1

  • DataArray.transpose with transpose_coords=True does not change coords order · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1326823221 https://github.com/pydata/xarray/issues/7294#issuecomment-1326823221 https://api.github.com/repos/pydata/xarray/issues/7294 IC_kwDOAMm_X85PFbc1 keewis 14808389 2022-11-24T20:39:03Z 2022-11-24T20:40:32Z MEMBER

transpose_coords is used to transpose coordinates with multiple dimensions: ```python In [1]: import xarray as xr ...: ...: ds = xr.tutorial.open_dataset("rasm") ...: ds.Tair.attrs.clear() ...: ds.Tair Out[1]: <xarray.DataArray 'Tair' (time: 36, y: 205, x: 275)> [2029500 values with dtype=float64] Coordinates: * time (time) object 1980-09-16 12:00:00 ... 1983-08-17 00:00:00 xc (y, x) float64 ... yc (y, x) float64 ... Dimensions without coordinates: y, x

In [2]: ds.Tair.transpose("x", "y", ..., transpose_coords=False) Out[2]: <xarray.DataArray 'Tair' (x: 275, y: 205, time: 36)> [2029500 values with dtype=float64] Coordinates: * time (time) object 1980-09-16 12:00:00 ... 1983-08-17 00:00:00 xc (y, x) float64 ... yc (y, x) float64 ... Dimensions without coordinates: x, y

In [3]: ds.Tair.transpose("x", "y", ..., transpose_coords=True) Out[3]: <xarray.DataArray 'Tair' (x: 275, y: 205, time: 36)> [2029500 values with dtype=float64] Coordinates: * time (time) object 1980-09-16 12:00:00 ... 1983-08-17 00:00:00 xc (x, y) float64 ... yc (x, y) float64 ... Dimensions without coordinates: x, y `` Interestingly,transpose_coordsis only an option forDataArray.transpose, and it defaults toTrue`. This means that the example from https://github.com/pydata/xarray/issues/7294#issue-1452123685 always does the same thing, so even if we did implement the reordering nothing would change.

As such, I'm -0.5 on changing the order in which the coordinates are stored, since the only time that order is used is the repr / HTML repr. In the past we have actually considered sorting the coordinates alphabetically, which did not happen because the coordinate names can be hashables of arbitrary types, and comparing a pair of hashables of different types is not easy.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   DataArray.transpose with transpose_coords=True does not change coords order 1452123685

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