issue_comments
7 rows where issue = 594669577 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- compose weighted with groupby, coarsen, resample, rolling etc. · 7 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1233445643 | https://github.com/pydata/xarray/issues/3937#issuecomment-1233445643 | https://api.github.com/repos/pydata/xarray/issues/3937 | IC_kwDOAMm_X85JhOML | jbusecke 14314623 | 2022-08-31T21:36:51Z | 2022-08-31T21:36:51Z | CONTRIBUTOR | I am interested in the coarsen with weights scenario that @dcherian and @mathause described here for a current project of ours. I solved the issue manually and its not that hard ```python import xarray as xr import numpy as np example data with weightsdata = np.arange(16).reshape(4,4).astype(float) add some nansdata[2,2] = np.nan data[1,1] = np.nan create some simple weightsweights = np.repeat(np.array([[1,2,1,3]]).T, 4, axis=1) weights da = xr.DataArray(data, dims=['x', 'y'], coords={'w':(['x','y'], weights)})
da
```
but I feel all of this is duplicating existing functionality (e.g. the masking of weights based on nans in the data) and might be sensibly streamlined into something like:
Happy to help but would definitely need some guidance on this one. I do believe that this would provide a very useful functionality for many folks who work with curvilinear grids and want to prototype things that depend on some sort of scale reduction (coarsening). Also cc'ing @TomNicholas who is involved in the same project 🤗 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
compose weighted with groupby, coarsen, resample, rolling etc. 594669577 | |
874796048 | https://github.com/pydata/xarray/issues/3937#issuecomment-874796048 | https://api.github.com/repos/pydata/xarray/issues/3937 | MDEyOklzc3VlQ29tbWVudDg3NDc5NjA0OA== | kuchaale 6815953 | 2021-07-06T14:11:52Z | 2021-07-06T14:11:52Z | NONE | Would
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
compose weighted with groupby, coarsen, resample, rolling etc. 594669577 | |
656060893 | https://github.com/pydata/xarray/issues/3937#issuecomment-656060893 | https://api.github.com/repos/pydata/xarray/issues/3937 | MDEyOklzc3VlQ29tbWVudDY1NjA2MDg5Mw== | mathause 10194086 | 2020-07-09T11:00:46Z | 2020-07-09T11:00:46Z | MEMBER | No that won't work. You need to mask the weights where the data is NaN. An untested and not very efficient way may be: ```python def coarsen_weighted_mean(da, weights, dims, skipna=None, boundary="exact"):
``` An example (without NaNs though): ```python import xarray as xr import numpy as np air = xr.tutorial.open_dataset("air_temperature").air weights = np.cos(np.deg2rad(air.lat)) we need to rename them from "lat"weights.name = "weights" c_w_m = coarsen_weighted_mean(air, weights, dict(lat=2), boundary="trim") to compare do it for one slicealt = air.isel(lat=slice(0, 2)).weighted(weights).mean("lat") compare if it is the samexr.testing.assert_allclose(c_w_m.isel(lat=0, drop=True), alt) ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
compose weighted with groupby, coarsen, resample, rolling etc. 594669577 | |
656035267 | https://github.com/pydata/xarray/issues/3937#issuecomment-656035267 | https://api.github.com/repos/pydata/xarray/issues/3937 | MDEyOklzc3VlQ29tbWVudDY1NjAzNTI2Nw== | roxyboy 8934026 | 2020-07-09T10:02:46Z | 2020-07-09T10:02:46Z | NONE | @mathause Does the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
compose weighted with groupby, coarsen, resample, rolling etc. 594669577 | |
655983882 | https://github.com/pydata/xarray/issues/3937#issuecomment-655983882 | https://api.github.com/repos/pydata/xarray/issues/3937 | MDEyOklzc3VlQ29tbWVudDY1NTk4Mzg4Mg== | mathause 10194086 | 2020-07-09T08:21:39Z | 2020-07-09T08:21:39Z | MEMBER | That's currently not possible. What you can try is the following:
but this only works if you don't have any NaNs. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
compose weighted with groupby, coarsen, resample, rolling etc. 594669577 | |
655726721 | https://github.com/pydata/xarray/issues/3937#issuecomment-655726721 | https://api.github.com/repos/pydata/xarray/issues/3937 | MDEyOklzc3VlQ29tbWVudDY1NTcyNjcyMQ== | dcherian 2448579 | 2020-07-08T20:01:59Z | 2020-07-08T20:01:59Z | MEMBER | @ahuang11 in #4210: I want to do something similar as xesmf's weighted regridding, but without the need to install esmpy which has a lot of dependencies. Are variations of the following possible?
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
compose weighted with groupby, coarsen, resample, rolling etc. 594669577 | |
611323242 | https://github.com/pydata/xarray/issues/3937#issuecomment-611323242 | https://api.github.com/repos/pydata/xarray/issues/3937 | MDEyOklzc3VlQ29tbWVudDYxMTMyMzI0Mg== | shoyer 1217238 | 2020-04-09T04:36:21Z | 2020-04-09T04:36:21Z | MEMBER | I think We could probably make both |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
compose weighted with groupby, coarsen, resample, rolling etc. 594669577 |
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 6