issue_comments
5 rows where issue = 293345254 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- roll doesn't handle periodic boundary conditions well · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
411275886 | https://github.com/pydata/xarray/issues/1875#issuecomment-411275886 | https://api.github.com/repos/pydata/xarray/issues/1875 | MDEyOklzc3VlQ29tbWVudDQxMTI3NTg4Ng== | ahuang11 15331990 | 2018-08-08T03:51:54Z | 2018-08-08T03:51:54Z | CONTRIBUTOR | Option 2 sounds good; I'll try putting together a pull request sometime, hopefully within a week! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
roll doesn't handle periodic boundary conditions well 293345254 | |
411222843 | https://github.com/pydata/xarray/issues/1875#issuecomment-411222843 | https://api.github.com/repos/pydata/xarray/issues/1875 | MDEyOklzc3VlQ29tbWVudDQxMTIyMjg0Mw== | shoyer 1217238 | 2018-08-07T22:25:16Z | 2018-08-07T22:25:16Z | MEMBER | Yes, it would be nice to change this to behavior (1) above. There are a few options here:
I am loathe to loose the name |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
roll doesn't handle periodic boundary conditions well 293345254 | |
411219752 | https://github.com/pydata/xarray/issues/1875#issuecomment-411219752 | https://api.github.com/repos/pydata/xarray/issues/1875 | MDEyOklzc3VlQ29tbWVudDQxMTIxOTc1Mg== | ahuang11 15331990 | 2018-08-07T22:11:42Z | 2018-08-07T22:11:42Z | CONTRIBUTOR | Just wanted to bump this! Would make my hack neater to interpolate across the prime meridian.
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
roll doesn't handle periodic boundary conditions well 293345254 | |
377655780 | https://github.com/pydata/xarray/issues/1875#issuecomment-377655780 | https://api.github.com/repos/pydata/xarray/issues/1875 | MDEyOklzc3VlQ29tbWVudDM3NzY1NTc4MA== | shoyer 1217238 | 2018-03-31T01:22:02Z | 2018-03-31T01:22:02Z | MEMBER | @mathause @rabernat any opinions here? My sense is that the current version of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
roll doesn't handle periodic boundary conditions well 293345254 | |
362104114 | https://github.com/pydata/xarray/issues/1875#issuecomment-362104114 | https://api.github.com/repos/pydata/xarray/issues/1875 | MDEyOklzc3VlQ29tbWVudDM2MjEwNDExNA== | fujiisoup 6815844 | 2018-01-31T23:19:27Z | 2018-01-31T23:19:27Z | MEMBER | I like the option 1. I agree that the circular coordinate is used in many physics fields (actually I'm not from geoscience and I also sometimes use the circular coordinate), but one confusing sene I can think of is when using it in radian, (0, 0.5 pi, pi ...). Manual overwite would be more explicit Another option could be to add a circular cooredinate class after #1603 is implemented? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
roll doesn't handle periodic boundary conditions well 293345254 |
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]);
user 3