issue_comments

Table actions

2 rows where author_association = "COLLABORATOR" and issue = 1329754426 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

issue 1

  • `Dataset.where()` incorrectly applies mask and creates new dimensions · 2 ✖

author_association 1

  • COLLABORATOR · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1206374954 https://github.com/pydata/xarray/issues/6879#issuecomment-1206374954 https://api.github.com/repos/pydata/xarray/issues/6879 IC_kwDOAMm_X85H59Iq headtr1ck 43316012 2022-08-05T12:09:59Z 2022-08-05T12:09:59Z COLLABORATOR

What is the use case in enlarging the 1-D array to a 3-D array with coordinates that it didn't have before?

It just follows the normal broadcasting behavior of xarray where any operation that involves two or more Datasets/DataArrays will broadcast all their dimensions.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `Dataset.where()` incorrectly applies mask and creates new dimensions 1329754426
1206358216 https://github.com/pydata/xarray/issues/6879#issuecomment-1206358216 https://api.github.com/repos/pydata/xarray/issues/6879 IC_kwDOAMm_X85H55DI headtr1ck 43316012 2022-08-05T11:48:49Z 2022-08-05T11:48:49Z COLLABORATOR

Thanks for the issue.

I would claim that this is the correct broadcasting behavior.

You could obtain your required result using python ds_mask = xr.Dataset({"t_2m_min_anom": mask, "t_2m_min_anom_stations": True}) data.where(ds_mask)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `Dataset.where()` incorrectly applies mask and creates new dimensions 1329754426

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