issue_comments

Table actions

4 rows where issue = 607229563 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 4

author_association 2

issue 1

  • Can Resample dim be spatial and not just datetime? · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1100655446 https://github.com/pydata/xarray/issues/4008#issuecomment-1100655446 https://api.github.com/repos/pydata/xarray/issues/4008 IC_kwDOAMm_X85BmqtW stale[bot] 26384082 2022-04-16T12:43:45Z 2022-04-16T12:43:45Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can Resample dim be spatial and not just datetime? 607229563
624196631 https://github.com/pydata/xarray/issues/4008#issuecomment-624196631 https://api.github.com/repos/pydata/xarray/issues/4008 MDEyOklzc3VlQ29tbWVudDYyNDE5NjYzMQ== shoyer 1217238 2020-05-05T17:27:14Z 2020-05-05T17:27:14Z MEMBER

I think resample for numeric axes would make a lot of sense -- it's weird that it's currently entirely datetime specific. This could probably be implemented on top of groupby_bins.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can Resample dim be spatial and not just datetime? 607229563
620018834 https://github.com/pydata/xarray/issues/4008#issuecomment-620018834 https://api.github.com/repos/pydata/xarray/issues/4008 MDEyOklzc3VlQ29tbWVudDYyMDAxODgzNA== chfite 59711987 2020-04-27T14:21:20Z 2020-04-27T14:21:20Z NONE

Thanks @dcherian for the input. coarsen looks like it would help me in what I'm doing some, but yeah having to specify "index space" is not as ideal in some cases. In theory it would be nice if in resample I could provide it the new coords I want it resampled to or something, similar to how you can feed new coords into interp. Then I guess it would be able to use those coordinates and groupby_bins under the hood to get the coarsened result? How feasible is it for someone with more xarray knowledge than myself to make this change?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can Resample dim be spatial and not just datetime? 607229563
619977995 https://github.com/pydata/xarray/issues/4008#issuecomment-619977995 https://api.github.com/repos/pydata/xarray/issues/4008 MDEyOklzc3VlQ29tbWVudDYxOTk3Nzk5NQ== dcherian 2448579 2020-04-27T13:14:16Z 2020-04-27T13:14:16Z MEMBER

Thanks for bringing this up, @chfite.

For a regularly spaced grid, coarsen will do what you want but note that it, like rolling, works in "index space" i.e. you specify number of points along each dimension: https://xarray.pydata.org/en/stable/computation.html#coarsen-large-arrays

resample builds on top of groupby so I think it would make sense to extend it to use groupby_bins when necessary. Then we would get "label space" coarsening.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can Resample dim be spatial and not just datetime? 607229563

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