issue_comments

Table actions

4 rows where author_association = "CONTRIBUTOR", issue = 1698626185 and user = 20118130 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

  • mgunyho · 4 ✖

issue 1

  • Implement multidimensional initial guess and bounds for `curvefit` · 4 ✖

author_association 1

  • CONTRIBUTOR · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1549151705 https://github.com/pydata/xarray/pull/7821#issuecomment-1549151705 https://api.github.com/repos/pydata/xarray/issues/7821 IC_kwDOAMm_X85cVi3Z mgunyho 20118130 2023-05-16T07:35:19Z 2023-05-16T07:40:46Z CONTRIBUTOR

I updated the type hints now (and also did a rebase just in case).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implement multidimensional initial guess and bounds for `curvefit` 1698626185
1537368210 https://github.com/pydata/xarray/pull/7821#issuecomment-1537368210 https://api.github.com/repos/pydata/xarray/issues/7821 IC_kwDOAMm_X85bomCS mgunyho 20118130 2023-05-07T09:23:16Z 2023-05-07T09:23:16Z CONTRIBUTOR

I implemented the broadcasting for bounds also. I hope it's not too ugly. Do you think the signature for p0 and bounds should be updated to explicitly allow only (tuples of) floats or DataArrays?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implement multidimensional initial guess and bounds for `curvefit` 1698626185
1537159048 https://github.com/pydata/xarray/pull/7821#issuecomment-1537159048 https://api.github.com/repos/pydata/xarray/issues/7821 IC_kwDOAMm_X85bny-I mgunyho 20118130 2023-05-06T14:56:05Z 2023-05-06T14:56:05Z CONTRIBUTOR

I just noticed that the docs for curvefit have some formatting issues, I think it's using single backticks instead of double backticks for code formatting. Should I add those to this PR as well?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implement multidimensional initial guess and bounds for `curvefit` 1698626185
1537142237 https://github.com/pydata/xarray/pull/7821#issuecomment-1537142237 https://api.github.com/repos/pydata/xarray/issues/7821 IC_kwDOAMm_X85bnu3d mgunyho 20118130 2023-05-06T13:25:41Z 2023-05-06T13:25:52Z CONTRIBUTOR

Hm the doctest failed because the result is off in the last decimal place. I can't reproduce it, even though I have the same versions of numpy 1.23.5 and scipy 1.10.1 in my env as what the CI says. Anyway, changed it in 3001eaf.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implement multidimensional initial guess and bounds for `curvefit` 1698626185

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