issue_comments
3 rows where user = 1924092 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- chris-b1 · 3 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 253624962 | https://github.com/pydata/xarray/issues/1044#issuecomment-253624962 | https://api.github.com/repos/pydata/xarray/issues/1044 | MDEyOklzc3VlQ29tbWVudDI1MzYyNDk2Mg== | chris-b1 1924092 | 2016-10-13T20:11:38Z | 2016-10-13T20:11:51Z | MEMBER | There could be some display options exposed to manage this - for instance I personally would not like a flat array - but see how it could make sense. Additionally / alternatively, the repr I'm talking (small slice of values laid out with coordinate labels) could called something other than |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Labeled repr 182638499 | |
| 248957341 | https://github.com/pydata/xarray/pull/964#issuecomment-248957341 | https://api.github.com/repos/pydata/xarray/issues/964 | MDEyOklzc3VlQ29tbWVudDI0ODk1NzM0MQ== | chris-b1 1924092 | 2016-09-22T16:34:44Z | 2016-09-22T16:34:44Z | MEMBER | @shoyer - I agree on 3) that it might too much to pack in to ``` python @xarray_gufunc @numba.guvectorize(['void(f8[:], f8[:])'], '(n)->()') def std_gufunc(arr, out): out[0] = np.std(arr) std_gufunc(arr, dims=('x',)) ``` https://gist.github.com/chris-b1/d28c6b8e78bf65ef7eb97e1095bc87f2 |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
New function for applying vectorized functions for unlabeled arrays to xarray objects 170779798 | |
| 248772865 | https://github.com/pydata/xarray/pull/964#issuecomment-248772865 | https://api.github.com/repos/pydata/xarray/issues/964 | MDEyOklzc3VlQ29tbWVudDI0ODc3Mjg2NQ== | chris-b1 1924092 | 2016-09-21T23:28:55Z | 2016-09-21T23:28:55Z | MEMBER | A few pieces of feedback trying this out. I'm basically learning xarray as I go (I ran into this right away), so weight appropriately. Usecase - I have a numba gufunc I want to apply to ``` @numba.guvectorize(['void(f8[:], f8[:])'], '(n)->()') def std_gufunc(arr, out): out[0] = np.std(arr) arr = xr.DataArray(np.random.randn(100, 100, 100), dims=('x', 'y', 'z')) ``` 1) The "obvious" thing doesn't work - maybe catch and show a nicer error message here
2) I personally found the non-string version of
3) It would be nice to take advantage of the existing gufunc signature in some way. Maybe this is a wrapper built on top or
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
New function for applying vectorized functions for unlabeled arrays to xarray objects 170779798 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
issue 2