issues

Table actions

4 rows where type = "pull" and user = 1386642 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

  • pull · 4 ✖

state 1

repo 1

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
484863660 MDExOlB1bGxSZXF1ZXN0MzEwNjQxMzE0 3262 [WIP] Implement 1D to ND interpolation nbren12 1386642 closed 0     9 2019-08-24T21:23:21Z 2020-12-17T01:29:12Z 2020-12-17T01:29:12Z CONTRIBUTOR   0 pydata/xarray/pulls/3262
  • [x] Closes #3252
  • [ ] Tests added
  • [ ] Passes black . && mypy . && flake8
  • [ ] Fully documented, including whats-new.rst for all changes and api.rst for new API
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3262/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
636611699 MDExOlB1bGxSZXF1ZXN0NDMyNzU0MDQ5 4144 Improve typehints of xr.Dataset.__getitem__ nbren12 1386642 closed 0     10 2020-06-10T23:33:41Z 2020-06-17T01:41:27Z 2020-06-15T11:25:53Z CONTRIBUTOR   0 pydata/xarray/pulls/4144

To resolve some common type-related errors, this PR adds some overload type hints to Dataset.__getitem__. Now mypy can correctly infer that hashable inputs return DataArrays.

  • [x] Closes #4125
  • [x] Passes isort -rc . && black . && mypy . && flake8
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/4144/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
261131958 MDExOlB1bGxSZXF1ZXN0MTQzNTExMTA3 1597 Add methods for combining variables of differing dimensionality nbren12 1386642 closed 0     46 2017-09-27T22:01:57Z 2019-07-05T15:59:51Z 2019-07-05T00:32:51Z CONTRIBUTOR   0 pydata/xarray/pulls/1597
  • [x] Closes #1317
  • [x] Tests added / passed
  • [x] Passes git diff upstream/master | flake8 --diff
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API

While working on #1317, I settled upon combining stack and to_array to create two dimensional numpy arrays given an xarray Dataset. Unfortunately, to_array automatically broadcasts the variables of dataset, which is not always a desirable behavior. For instance, I was trying to combine precipitation (a horizontal field) and temperature (a 3D field) into one array.

This PR enables this by adding two new methods to xarray: - Dataset.stack_cat, and - DataArray.unstack_cat.

stack_cat uses stack, expand_dims, and concat to reshape a Dataset into a Dataarray with a helpful MultiIndex, and unstack_cat reverses the process.

I implemented this functionality as a new method since to_array is such a clean method already. I really appreciate your thoughts on this. Thanks!

cc @jhamman @shoyer 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1597/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
294089233 MDExOlB1bGxSZXF1ZXN0MTY2OTQ5Nzcw 1885 Raise when pcolormesh coordinate is not sorted nbren12 1386642 closed 0     18 2018-02-03T06:37:34Z 2018-02-18T19:26:36Z 2018-02-18T19:06:31Z CONTRIBUTOR   0 pydata/xarray/pulls/1885
  • [x] Closes #1852 (remove if there is no corresponding issue, which should only be the case for minor changes)
  • [x] Tests added (for all bug fixes or enhancements)
  • [x] Tests passed (for all non-documentation changes)

I added a simple warning to _infer_interval_breaks in xarray/plot/plot.py. The warning does not currently say the name of the coordinate, because that would requiring introducing a new function or potentially passing a name argument, which seems overly complicated for such a small dit. Hopefully, this isn't a problem because the user can easily figure out which coordinate is not sorted by process of elimination.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1885/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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