issue_comments

Table actions

2 rows where issue = 57254455 and user = 1794715 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

  • ebrevdo · 2 ✖

issue 1

  • Add head(), tail() and thin() methods? · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
73815254 https://github.com/pydata/xarray/issues/319#issuecomment-73815254 https://api.github.com/repos/pydata/xarray/issues/319 MDEyOklzc3VlQ29tbWVudDczODE1MjU0 ebrevdo 1794715 2015-02-11T00:39:55Z 2015-02-11T00:39:55Z CONTRIBUTOR

seems like for, e.g., head, you can pass either a single dimension or multiple ones (e.g., either as **kwargs or a dictionary) and use those as the start dimension.

that said, about naming conventions, i think for tensors the most common convention is definitely slice() (which is implemented as isel). head/tail can be implemented in terms of slice().

e.g.: ds.slice(dim1=3, dim2=(1,4), dim3=(1,None,5)) -- or -- ds.slice({'dim1': 3, 'dim2': (1,4), 'dim3': (1, None, 5)})

head/tail/whatever are easy calls to this and you can have that in the documentation. as a result, people won't get confused because they understand slice.

On Tue, Feb 10, 2015 at 4:14 PM, Stephan Hoyer notifications@github.com wrote:

@ebrevdo https://github.com/ebrevdo yes, I think we probably need to stick to the pandas/numpy convention for the meaning of take.

My inspiration for these names was the head() and tail() methods in pandas, which are quite convenient. But it's not entirely clear how/if these generalize cleanly to N-dimensions. I suppose take_first and take_last could be an improvement over head/tail.

— Reply to this email directly or view it on GitHub https://github.com/xray/xray/issues/319#issuecomment-73812481.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add head(), tail() and thin() methods? 57254455
73810816 https://github.com/pydata/xarray/issues/319#issuecomment-73810816 https://api.github.com/repos/pydata/xarray/issues/319 MDEyOklzc3VlQ29tbWVudDczODEwODE2 ebrevdo 1794715 2015-02-11T00:00:14Z 2015-02-11T00:00:14Z CONTRIBUTOR

Clojure conventions: .take, .take_last get the first n and last n pandas/ndarray conventions: .take([3,4,5]) selects rows 3,4,5.

probably want to be consistent with one of these.

On Tue, Feb 10, 2015 at 3:28 PM, Stephan Hoyer notifications@github.com wrote:

These would be shortcuts for isel/slice syntax: - ds.head(time=5) -> ds.isel(time=slice(5)): select the first five time values - ds.tail(time=5) -> ds.isel(time=slice(-5, None)): select the last five time values - ds.subsample(time=5) -> ds.isel(time=slice(None, None, 5)): select every 5th time value

— Reply to this email directly or view it on GitHub https://github.com/xray/xray/issues/319.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add head(), tail() and thin() methods? 57254455

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