issues

Table actions

4 rows where user = 223250 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)

state 2

type 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
944714417 MDExOlB1bGxSZXF1ZXN0NjkwMTUzNjQ1 5603 Allow no padding for rolling windows kmsquire 223250 open 0     15 2021-07-14T19:04:55Z 2024-03-21T02:42:46Z   CONTRIBUTOR   0 pydata/xarray/pulls/5603
  • [x] Fixes #4743
  • [x] Tests added
  • [x] Passes pre-commit run --all-files
  • [ ] User visible changes (including notable bug fixes) are documented in whats-new.rst

Related to #2007.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/5603/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
445045305 MDExOlB1bGxSZXF1ZXN0Mjc5NTc4Mzgw 2968 Add examples for `DataArrayRolling.reduce()` kmsquire 223250 closed 0     7 2019-05-16T16:17:00Z 2019-06-04T14:47:09Z 2019-06-04T14:47:08Z CONTRIBUTOR   0 pydata/xarray/pulls/2968
  • ~~When reducing over a rolling window, DataArrayRolling.reduce() only returns values where the complete rolling window is fully conatined within the base array; the remaining locations where the window overlaps the array border are filled with NaN~~
  • ~~However, in some situations, it is desirable to obtain values from the reducer function for all locations. This commit adds a keyword argument, include_border, to DataArrayRolling.reduce() and DataSetRolling.reduce() to allow this behavior.~~

~~If this seems okay, I have some questions:~~

~~1. Should this behavior be added to specific reducing functions (sum, mean, etc.)? As an alternative, all of the specialized functions for DataArrayRolling have corresponding numpy nan* functions, so support could be added for those. (The current PR is still useful for other reducing functions, which is my use case.)~~ ~~2. I don't use dask, so I don't know if this is needed/desired for the dask versions of these functions.~~

As @mathause pointed out, the functionality desired already exists by passing min_periods=1 to DataArray.rolling(). So this MR has been updated to simply include some examples for DataArrayRolling.reduce()

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2968/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
445032612 MDExOlB1bGxSZXF1ZXN0Mjc5NTY4MjYx 2967 Fix rolling.constuct() example kmsquire 223250 closed 0     1 2019-05-16T15:50:17Z 2019-05-16T15:55:16Z 2019-05-16T15:55:16Z CONTRIBUTOR   0 pydata/xarray/pulls/2967

The example was using the wrong name for the function (to_datarray), and used the wrong dimension for the window.

Cc: @fujiisoup, who added this in #1837

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2967/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
409618228 MDExOlB1bGxSZXF1ZXN0MjUyNTU1OTQx 2767 Add `Dataset.drop_dims` kmsquire 223250 closed 0     11 2019-02-13T04:15:04Z 2019-04-12T07:26:07Z 2019-03-03T19:39:40Z CONTRIBUTOR   0 pydata/xarray/pulls/2767
  • [x] Closes #1949
  • [x] Tests added
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2767/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]);