issue_comments

Table actions

1 row where issue = 1157140667 and user = 39069044 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

  • slevang · 1 ✖

issue 1

  • Handle scipy fitting errors in `xarray.curve_fit` · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1057116313 https://github.com/pydata/xarray/issues/6317#issuecomment-1057116313 https://api.github.com/repos/pydata/xarray/issues/6317 IC_kwDOAMm_X84_AlCZ slevang 39069044 2022-03-02T16:24:37Z 2022-03-02T16:24:37Z CONTRIBUTOR

These errors can often be eliminated by passing appropriate initial guesses for each parameter through the p0 argument (which it looks like you're already doing), and/or by passing additional kwargs through to scipy.optimize.leastsq(), like ftol and maxfev which set the fit tolerance and max number of iterations.

Even so, there will be cases where some of your data just doesn't fit the desired function and you want to move on and return a result anyway. Your proposal seems fine as long as errors are raised by default and the documentation adequately describes the behavior when set to True.

 
{
    "total_count": 5,
    "+1": 5,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Handle scipy fitting errors in `xarray.curve_fit` 1157140667

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