issue_comments

Table actions

4 rows where author_association = "MEMBER" and issue = 577030502 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 1

  • Problems plotting long model control runs with gregorian calendar · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
596023908 https://github.com/pydata/xarray/issues/3841#issuecomment-596023908 https://api.github.com/repos/pydata/xarray/issues/3841 MDEyOklzc3VlQ29tbWVudDU5NjAyMzkwOA== spencerkclark 6628425 2020-03-07T00:55:42Z 2020-03-07T00:55:42Z MEMBER

No worries! Yeah, it would be great if you could post an issue there; I think you can probably come up with a more minimal example (i.e. take xarray out of it and use some synthetic data with cftime dates near year 0 as the x-coordinate).

The fact that cftime.DatetimeProlepticGregorian supports years <= -1 and >= 1, but not year 0, makes things a bit awkward, but I think is based on CF conventions.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Problems plotting long model control runs with gregorian calendar 577030502
595877540 https://github.com/pydata/xarray/issues/3841#issuecomment-595877540 https://api.github.com/repos/pydata/xarray/issues/3841 MDEyOklzc3VlQ29tbWVudDU5NTg3NzU0MA== spencerkclark 6628425 2020-03-06T17:32:55Z 2020-03-06T17:32:55Z MEMBER

I think this is probably best fixed in nc-time-axis. It looks like it is creating generic datetimes with year 0 somewhere in here, which cftime does not allow for the proleptic Gregorian calendar. The error gets thrown when trying to apply the calendar type in utime.date2num(ticks).

I'm fine though with you posting this here for visibility; I'm not sure how active the nc-time-axis repo is.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Problems plotting long model control runs with gregorian calendar 577030502
595852733 https://github.com/pydata/xarray/issues/3841#issuecomment-595852733 https://api.github.com/repos/pydata/xarray/issues/3841 MDEyOklzc3VlQ29tbWVudDU5NTg1MjczMw== mathause 10194086 2020-03-06T16:38:07Z 2020-03-06T16:38:07Z MEMBER

It looks like you can set xlim in da.plot.line - could you test this?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Problems plotting long model control runs with gregorian calendar 577030502
595850628 https://github.com/pydata/xarray/issues/3841#issuecomment-595850628 https://api.github.com/repos/pydata/xarray/issues/3841 MDEyOklzc3VlQ29tbWVudDU5NTg1MDYyOA== max-sixty 5635139 2020-03-06T16:33:21Z 2020-03-06T16:33:21Z MEMBER

Thanks for the report.

This isn't immediately helpful to you but: any ideas why xarray isn't in the stack trace? Is this a plotting oddity?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Problems plotting long model control runs with gregorian calendar 577030502

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