issue_comments

Table actions

4 rows where issue = 96211612 and user = 25473287 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • JiaweiZhuang · 4 ✖

issue 1

  • API for multi-dimensional resampling/regridding · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
325717752 https://github.com/pydata/xarray/issues/486#issuecomment-325717752 https://api.github.com/repos/pydata/xarray/issues/486 MDEyOklzc3VlQ29tbWVudDMyNTcxNzc1Mg== JiaweiZhuang 25473287 2017-08-29T16:23:07Z 2017-11-09T02:10:28Z NONE

I've wrapped ESMF/ESMPy by xarray: https://github.com/JiaweiZhuang/xESMF

It supports remapping between arbitrary quadrilateral grids, using ESMF's regridding algorithms including bilinear, conservative, nearest neighbour, etc... See this notebook for an example.

The package is still preliminary but it already works. See "Issues & Plans" in the main page for more details.

 
{
    "total_count": 7,
    "+1": 7,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   API for multi-dimensional resampling/regridding 96211612
343024897 https://github.com/pydata/xarray/issues/486#issuecomment-343024897 https://api.github.com/repos/pydata/xarray/issues/486 MDEyOklzc3VlQ29tbWVudDM0MzAyNDg5Nw== JiaweiZhuang 25473287 2017-11-09T02:09:13Z 2017-11-09T02:09:13Z NONE

I am thinking about the API design for xESMF (JiaweiZhuang/xESMF#9). Any comments are welcome 😃

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   API for multi-dimensional resampling/regridding 96211612
325998681 https://github.com/pydata/xarray/issues/486#issuecomment-325998681 https://api.github.com/repos/pydata/xarray/issues/486 MDEyOklzc3VlQ29tbWVudDMyNTk5ODY4MQ== JiaweiZhuang 25473287 2017-08-30T13:58:00Z 2017-08-30T13:58:00Z NONE

@ocefpaf Any plan for Python3-compatible ESMPy? I only see Python2.7 here: https://github.com/conda-forge/esmpy-feedstock

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   API for multi-dimensional resampling/regridding 96211612
325861556 https://github.com/pydata/xarray/issues/486#issuecomment-325861556 https://api.github.com/repos/pydata/xarray/issues/486 MDEyOklzc3VlQ29tbWVudDMyNTg2MTU1Ng== JiaweiZhuang 25473287 2017-08-30T02:36:08Z 2017-08-30T03:25:43Z NONE

@rabernat Thanks for the suggestion! I'll add tests&docs when time allows.

If you want to look into details: The package contains the two layers (explained in the "Design Idea" section). The first layer has nothing to do with xarray, but just provides a convenient way (only with numpy) to access a useful subset of ESMPy functions. This layer is important because ESMPy's API is too complicated, but once it is done it doesn't need to be changed too often. The second layer wraps the first layer using xarray. Most of the crafts will be added to the second layer.

As a temporary workaround, I've added another notebook for using the low-level wrapper, for interested developers.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   API for multi-dimensional resampling/regridding 96211612

Advanced export

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

CSV options: 

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