issue_comments

Table actions

3 rows where issue = 104484316 and user = 1217238 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

  • shoyer · 3 ✖

issue 1

  • CDO-like convenience methods to select times · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
427335183 https://github.com/pydata/xarray/issues/557#issuecomment-427335183 https://api.github.com/repos/pydata/xarray/issues/557 MDEyOklzc3VlQ29tbWVudDQyNzMzNTE4Mw== shoyer 1217238 2018-10-05T11:33:45Z 2018-10-05T11:33:45Z MEMBER

dataset.time.dt.year.isin(elnino_years) should work already with.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   CDO-like convenience methods to select times 104484316
427279439 https://github.com/pydata/xarray/issues/557#issuecomment-427279439 https://api.github.com/repos/pydata/xarray/issues/557 MDEyOklzc3VlQ29tbWVudDQyNzI3OTQzOQ== shoyer 1217238 2018-10-05T07:59:47Z 2018-10-05T08:00:28Z MEMBER

I don’t think there’s an easy way to this with vectorized indexing, but if we supported multidimensional indexing with boolean keys as proposed in https://github.com/pydata/xarray/issues/1887 (equivalent to where with drop=True) we could write pr_dataset[pr_dataset['time.year'].isin(elnino_years)]

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   CDO-like convenience methods to select times 104484316
137182504 https://github.com/pydata/xarray/issues/557#issuecomment-137182504 https://api.github.com/repos/pydata/xarray/issues/557 MDEyOklzc3VlQ29tbWVudDEzNzE4MjUwNA== shoyer 1217238 2015-09-02T17:37:56Z 2015-09-02T17:37:56Z MEMBER

Currently, the way to do this is to create a boolean indexer, with something like the following:

pr_dataset.sel(time=np.in1d(pr_dataset['time.year'], elnino_years))

I agree that this is overly verbose and we can come up with something better. I'm not quite happy with selyear, though: - It's ambiguous which datetime variable the year refers do (there can be more than one time variable on some datasets). - I'm also not a big fan of adding a bunch of new API methods that are datetime specific -- it creates a lot of noise (pandas has an issue with this).

Something like pr_dataset.sel(year=elnino_years) would be the ideal fix for this second concern (we've discussed this in another issue, can't remember which one now), but it's still ambiguous which time variable it refers to.

So, some other possible ways to spell this: 1. pr_dataset.sel('time', year=elnino_years) 2. pr_dataset.sel('time.year', elnino_years) 3. pr_dataset.sel.time.year(elnino_years)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   CDO-like convenience methods to select times 104484316

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