issues
5 rows where comments = 9 and user = 1217238 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
390774883 | MDU6SXNzdWUzOTA3NzQ4ODM= | 2605 | Pad method | shoyer 1217238 | closed | 0 | 9 | 2018-12-13T17:08:25Z | 2020-03-19T14:41:49Z | 2020-03-19T14:41:49Z | MEMBER | It would be nice to have a generic In particular, It probably makes sense to linearly extrapolate coordinates along padded dimensions, as long as they are regularly spaced. This might use heuristics and/or a keyword argument. I don't have a plans to work on this in the near term. It could be a good project of moderate complexity for a new contributor. |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/2605/reactions", "total_count": 5, "+1": 5, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
489270698 | MDU6SXNzdWU0ODkyNzA2OTg= | 3280 | Deprecation cycles to finish for xarray 0.13 | shoyer 1217238 | closed | 0 | 9 | 2019-09-04T16:37:26Z | 2019-09-17T18:50:05Z | 2019-09-17T18:50:05Z | MEMBER | Clean-ups we should definitely do:
- [x] remove deprecated options from Clean-ups to consider:
- [x] switch the default reduction dimension of groupby and resample? (https://github.com/pydata/xarray/pull/2366) This has been giving a FutureWarning since v0.11.0, released back in November 2018. We could also potentially push this back to 0.14, but these warnings are a little annoying...
- [x] deprecate |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3280/reactions", "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 1, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
324486173 | MDExOlB1bGxSZXF1ZXN0MTg5MDg0MTg4 | 2162 | Test suite: explicitly ignore irrelevant warnings | shoyer 1217238 | closed | 0 | 9 | 2018-05-18T17:06:03Z | 2018-05-29T04:34:54Z | 2018-05-29T04:34:47Z | MEMBER | 0 | pydata/xarray/pulls/2162 | Includes silencing two warnings that show up in xarray's public API:
``` In [1]: import numpy as np In [2]: import xarray as xr In [3]: array = xr.DataArray([np.datetime64('NaT')]) In [4]: array[0].equals(array[0]) /Users/shoyer/dev/xarray/xarray/core/duck_array_ops.py:148: FutureWarning: In the future, 'NAT == x' and 'x == NAT' will always be False. flag_array = (arr1 == arr2) Out[16]: True ``` Fixes #2161
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/2162/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | pull | |||||
169547144 | MDU6SXNzdWUxNjk1NDcxNDQ= | 946 | List of projects using xarray | shoyer 1217238 | closed | 0 | 9 | 2016-08-05T07:38:13Z | 2018-05-14T21:04:31Z | 2018-05-14T21:04:31Z | MEMBER | I'm particularly interested in projects that we should highlight in our docs and other publications, either as evidence of the impact of xarray or because other xarray users would find it useful to know about them. We could put together an "Xarray ecosystem" docs page like pandas. What I have so far falls into three categories: Tools for analyzing global climate model output with xarray: - xgcm: for analyzing general circulation model output data - oocgcm: analysis of large gridded geophysical dataset - mpas_xarray: wrapper to allow input of mpas data into xarray - marc_analysis: Analysis package for CESM/MARC experiments and output Other weather/climate specific tools: - windspharm: wind spherical harmonics - eofs: empirical orthogonal functions - infinite-diff: xarray-based finite-differencing - aospy: Climate data analysis, database, and visualization Non-climate: - Datashader: visualization for large data - cesium: machine learning for time series analysis - ptsa: EEG Time Series Analysis - pyGDX: GDX file data access - pycalphad: Computational Thermodynamics in Python |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/946/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
217287113 | MDExOlB1bGxSZXF1ZXN0MTEyNzc0NzE0 | 1330 | If join='exact', raise an error for non-aligned objects | shoyer 1217238 | closed | 0 | 9 | 2017-03-27T15:37:55Z | 2017-05-31T01:09:14Z | 2017-05-31T01:08:45Z | MEMBER | 0 | pydata/xarray/pulls/1330 |
This is useful for asserting that objects are identical instead of aligning in xarray operations. For example:
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1330/reactions", "total_count": 1, "+1": 1, "-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
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]);