issue_comments

Table actions

1 row where author_association = "NONE", issue = 100980878 and user = 1151830 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

  • jsbj · 1 ✖

issue 1

  • Having trouble with time dim of CMIP5 dataset · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
134757704 https://github.com/pydata/xarray/issues/531#issuecomment-134757704 https://api.github.com/repos/pydata/xarray/issues/531 MDEyOklzc3VlQ29tbWVudDEzNDc1NzcwNA== jsbj 1151830 2015-08-25T22:15:22Z 2015-08-25T22:15:22Z NONE

Thanks Daniel, that workaround totally works.

-j

2015-08-14 15:26 GMT-04:00 Daniel Rothenberg notifications@github.com:

Hi @jsbj https://github.com/jsbj,

The fancy indexing notation you're trying to use only works when xray successfully decodes the time dimension. As discussed in the documentation here http://xray.readthedocs.org/en/stable/time-series.html#creating-datetime64-data, this only works when the year of record falls between 1678 and 2262. Since you have years 2262-2300 in your dataset, this is a feature - xray is failing gracefully.

There are a few current open discussions on this behavior, which is an issue higher up the python chain with numpy: 1. time decoding error with "days since" https://github.com/xray/xray/issues/521 2. Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' https://github.com/xray/xray/pull/522 3. ocefpaf - Loading non-standard dates with cf_units https://ocefpaf.github.io/python4oceanographers/blog/2015/08/10/cf_units_and_time/ 4. numpy - Non-standard Calendar Support https://github.com/numpy/numpy/issues/6207

For now, a very simple hack would be to re-compute your time units so that they're re-based, say, with units 'days since 1700-01-01 00:00:00'. That way all of them would fit within the permissible range to use the decoding routine built into xray. You could simply pass the decode_cf=False flag when you open the dataset, modify the non-decoded time array and units, then run xray.decode_cf() on the modified dataset.

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

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Having trouble with time dim of CMIP5 dataset 100980878

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