issue_comments

Table actions

2 rows where user = 5189118 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • bennyrowland · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
811411463 https://github.com/pydata/xarray/issues/5094#issuecomment-811411463 https://api.github.com/repos/pydata/xarray/issues/5094 MDEyOklzc3VlQ29tbWVudDgxMTQxMTQ2Mw== bennyrowland 5189118 2021-03-31T20:00:40Z 2021-03-31T20:00:40Z NONE

Indeed, it looks like that will solve my problem when it gets merged. I did a search for existing issues but missed 4489 as a PR. I will close this and keep an eye on 4489 instead. Thanks for bringing it to my attention.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   exact align should support a tolerance for agreement in coordinates 844827026
805783942 https://github.com/pydata/xarray/issues/3868#issuecomment-805783942 https://api.github.com/repos/pydata/xarray/issues/3868 MDEyOklzc3VlQ29tbWVudDgwNTc4Mzk0Mg== bennyrowland 5189118 2021-03-24T12:33:57Z 2021-03-24T12:33:57Z NONE

Would it be conceivable to implement an alternative form of coordinate index which is explicitly a linear coordinate axis, storing only a first point and a step (possibly a last point but that would obviously be redundant with the length of the dimension). This would be trivial to pad via linear extrapolation and the pad function would just have to ask the coordinate to pad itself. This could also in principle extend to other coordinates like a periodic one etc., although I don't personally have a use for those. Coordinates that don't know how to handle being padded can use NaN as currently. I guess that this is one of the things that could be enabled by #1603?

My use case is in MRI reconstruction where we frequently have asymmetric datasets and need to pad them to be symmetric before an IFT. I am using xrft which is great but makes a fuss if the coordinates are not correctly linear and centred on the origin. The degree of asymmetry and the step size change from dataset to dataset, so it is not trivial to assemble the necessary new coordinate values for @fujiisoup's proposed solution.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   What should pad do about IndexVariables? 584461380

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