issue_comments

Table actions

5 rows where issue = 43442970 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

author_association 2

issue 1

  • WIP: convert to/from cdms2 variables · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
67614270 https://github.com/pydata/xarray/pull/236#issuecomment-67614270 https://api.github.com/repos/pydata/xarray/issues/236 MDEyOklzc3VlQ29tbWVudDY3NjE0Mjcw shoyer 1217238 2014-12-19T09:11:20Z 2014-12-19T09:11:20Z MEMBER

@DamienIrving I'm going to merge this now. I did add support for encoding/decoding time information, but you should probably still consider this experimental for now. Please do let me know how it works for you when you get the chance to try it out.

I'll be releasing v0.3.2 with this within the next few days.

 
{
    "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
56918016 https://github.com/pydata/xarray/pull/236#issuecomment-56918016 https://api.github.com/repos/pydata/xarray/issues/236 MDEyOklzc3VlQ29tbWVudDU2OTE4MDE2 shoyer 1217238 2014-09-26T04:25:08Z 2014-09-26T04:25:21Z MEMBER

@DamienIrving Yes, that does help.

The main thing is I'm pretty sure CDAT's climatological related functions can't handle dates in the form of a np.datetime64 array (which xray uses), so we'll probably need to convert back into CF conventions style "days since YYYY-MM-DD".

 
{
    "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
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 cdutil library to calculate a seasonal climatology or something, you have to use cdutil.setTimeBounds() to specify the time bounds of your data (i.e. whether it is daily, monthly, etc).

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 data), you can use data.getTime().asComponentTime().

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
56452068 https://github.com/pydata/xarray/pull/236#issuecomment-56452068 https://api.github.com/repos/pydata/xarray/issues/236 MDEyOklzc3VlQ29tbWVudDU2NDUyMDY4 shoyer 1217238 2014-09-22T22:15:50Z 2014-09-22T22:15:50Z MEMBER

So I understand cdat uses masked arrays for missing values. How does it handle dates?

On Mon, Sep 22, 2014 at 3:13 PM, Damien Irving notifications@github.com wrote:

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 cdutil and genutil.

Reply to this email directly or view it on GitHub: https://github.com/xray/xray/pull/236#issuecomment-56451763

 
{
    "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 cdutil and genutil. 

{
    "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

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