issue_comments
4 rows where author_association = "NONE" and user = 2062210 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- DamienIrving · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
56758849 | https://github.com/pydata/xarray/pull/236#issuecomment-56758849 | https://api.github.com/repos/pydata/xarray/issues/236 | MDEyOklzc3VlQ29tbWVudDU2NzU4ODQ5 | DamienIrving 2062210 | 2014-09-25T00:28:11Z | 2014-09-25T00:28:11Z | NONE | I'm not sure exactly how it handles dates under the hood, however as a user before using a convenience function from the To view the time axis of a cdms2 transient variable in a convenient YYYY-MM-DD HH:MM:SS format (e.g. let's say that variable's name is Does that help? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP: convert to/from cdms2 variables 43442970 | |
56451763 | https://github.com/pydata/xarray/pull/236#issuecomment-56451763 | https://api.github.com/repos/pydata/xarray/issues/236 | MDEyOklzc3VlQ29tbWVudDU2NDUxNzYz | DamienIrving 2062210 | 2014-09-22T22:13:11Z | 2014-09-22T22:13:11Z | NONE | Your approach looks good to me. All people need to be able to do is move to and from cdms2 transient variables and then they'll have access to all the convenience functions defined in cdat-lite libraries like |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP: convert to/from cdms2 variables 43442970 | |
56313445 | https://github.com/pydata/xarray/issues/133#issuecomment-56313445 | https://api.github.com/repos/pydata/xarray/issues/133 | MDEyOklzc3VlQ29tbWVudDU2MzEzNDQ1 | DamienIrving 2062210 | 2014-09-21T21:29:11Z | 2014-09-21T21:29:11Z | NONE | Happy to test it out for you. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Functions for converting to and from CDAT cdms2 variables 33639540 | |
56258103 | https://github.com/pydata/xarray/issues/133#issuecomment-56258103 | https://api.github.com/repos/pydata/xarray/issues/133 | MDEyOklzc3VlQ29tbWVudDU2MjU4MTAz | DamienIrving 2062210 | 2014-09-20T06:05:19Z | 2014-09-20T06:05:19Z | NONE | @shoyer I love this suggested enhancement. If I could use xray and CDAT interchangeably, then I'd add xray into my workflow immediately (I'd image many other people would too, as CDAT has a fairly large user base). The first thing I'd say is that you don't need to install all of UV-CDAT to get the useful modules. Instead, people have developed cdat-lite, which strips away all the visualisation stuff associated with UV-CDAT and just leaves the core convenience functions for calculating climatologies etc (i.e. it strips away the UV bit and just leaves the CDAT). With the emergence of conda and binstar, it's now very easy to install cdat-lite with Anaconda. This page should be all you need: https://binstar.org/ajdawson/cdat-lite |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Functions for converting to and from CDAT cdms2 variables 33639540 |
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