issues
4 rows where user = 25473287 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date), closed_at (date)
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at ▲ | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
242181620 | MDU6SXNzdWUyNDIxODE2MjA= | 1475 | Allow DataArray to hold cell boundaries as coordinate variables | JiaweiZhuang 25473287 | open | 0 | 14 | 2017-07-11T20:58:44Z | 2023-08-24T13:21:05Z | NONE | Cell boundaries can be either N+1 sized arrays as suggested by xgcm/xmitgcm#15, or (N,2) sized arrays as suggested by the CF convention. However, a DataArray cannot hold both kinds of coordinate variables because they contain a new dimension. If you try to assign a new coordinate to a DataArray by On the other hand, if your DataSet contains cell boundary variables (for example, #667), the bounds will be dropped when you extract a single variable into a DataArray. Having cell bounds available in a DataArray is important for a couple of applications:
Plotting or regridding will work fine if you pass cell bounds as an additional argument to a wrapper function. However, having a single DataArray object containing boundary information seems like a more elegant solution. Is it possible to let DataArray accept N+1 sized coordinate variables, and be able to inherit them from the parent DataSet? If that's too drastic, is it possible to write an accessor to extend DataArray's capability? Say, a "bound" accessor for a new attribute |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1475/reactions", "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 1 } |
xarray 13221727 | issue | ||||||||
340486433 | MDU6SXNzdWUzNDA0ODY0MzM= | 2281 | Does interp() work on curvilinear grids (2D coordinates) ? | JiaweiZhuang 25473287 | open | 0 | 28 | 2018-07-12T04:36:43Z | 2020-09-04T19:24:32Z | NONE | I am evaluating Seems like That's the test data:
That's a simple destination grid:
I would expect a syntax like:
But I got
@crusaderky @fujiisoup |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/2281/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | issue | ||||||||
282916278 | MDU6SXNzdWUyODI5MTYyNzg= | 1789 | Broken link to github on ReadTheDocs | JiaweiZhuang 25473287 | closed | 0 | 8 | 2017-12-18T15:24:04Z | 2018-10-25T16:24:27Z | 2018-10-25T16:24:27Z | NONE | The "Edit on GitHub" button on ReadTheDocs is linked to https://github.com/pydata/xarray/blob/origin/stable/doc/index.rst which doesn't exist. The correct URL would be without "origin": https://github.com/pydata/xarray/blob/stable/doc/index.rst |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1789/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
298834332 | MDU6SXNzdWUyOTg4MzQzMzI= | 1931 | apply_ufunc produces illegal coordinate sizes | JiaweiZhuang 25473287 | closed | 0 | 5 | 2018-02-21T03:58:19Z | 2018-05-31T15:40:04Z | 2018-05-31T15:40:04Z | NONE | If Would it be more natural to drop the core coordinate by default? This is safer (will not produce illegal NetCDF file) and also makes more physical sense (the core coordinate is likely to change). I'd like use Output of
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1931/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issues] ( [id] INTEGER PRIMARY KEY, [node_id] TEXT, [number] INTEGER, [title] TEXT, [user] INTEGER REFERENCES [users]([id]), [state] TEXT, [locked] INTEGER, [assignee] INTEGER REFERENCES [users]([id]), [milestone] INTEGER REFERENCES [milestones]([id]), [comments] INTEGER, [created_at] TEXT, [updated_at] TEXT, [closed_at] TEXT, [author_association] TEXT, [active_lock_reason] TEXT, [draft] INTEGER, [pull_request] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [state_reason] TEXT, [repo] INTEGER REFERENCES [repos]([id]), [type] TEXT ); CREATE INDEX [idx_issues_repo] ON [issues] ([repo]); CREATE INDEX [idx_issues_milestone] ON [issues] ([milestone]); CREATE INDEX [idx_issues_assignee] ON [issues] ([assignee]); CREATE INDEX [idx_issues_user] ON [issues] ([user]);