issue_comments
1 row where author_association = "MEMBER", issue = 548475127 and user = 1197350 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Different data values from xarray open_mfdataset when using chunks · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
573455048 | https://github.com/pydata/xarray/issues/3686#issuecomment-573455048 | https://api.github.com/repos/pydata/xarray/issues/3686 | MDEyOklzc3VlQ29tbWVudDU3MzQ1NTA0OA== | rabernat 1197350 | 2020-01-12T20:41:53Z | 2020-01-12T20:41:53Z | MEMBER | Thanks for the useful issue @abarciauskas-bgse and valuable test @dmedv. I believe this is fundamentally a Dask issue. In general, Dask's algorithms do not guarantee numerically identical results for different chunk sizes. Roundoff errors accrue slightly differently based on how the array is split up. These errors are usually acceptable to users. For example, 290.13754 vs 290.13757, the error is in the 8th significant digit, 1 part in 100,00,000. Since there are only 65,536 16-bit integers (the original data type in the netCDF file), this seems more than adequate precision to me. Calling There appears to be a second issue here related to fill values, but I haven't quite grasped whether we think there is a bug.
There may be a reason why these operations are coupled. Would have to look more closely at the code to know for sure. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Different data values from xarray open_mfdataset when using chunks 548475127 |
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 1