You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should return confidence intervals on our parameter fits (probably as a model.confidence_ attribute). The standard deviation can be calculated by taking the square root of the diagonal elements in the covariance matrix that is returned by leastsq (np.sqrt(np.diag(pcov)).
It would also be awesome if the predict method could predict the upper and lower confidence interval ranges too!
The text was updated successfully, but these errors were encountered:
We should directly add them to the plot as well. Maybe we can render a nice seaborn image as an object where getting the attribute will return the plot, or give the object a plot function with nice defaults.
I like the idea of trying to add some plotting. I've got the formatted matplotlib figure from the tutorials leading up to Hack Week. I also think it'd be cool to generate altair Nyquist plots that have tooltips.
Added initial support for confidence intervals in 398c241
Right now it basically takes N=1000 uniform samples over the +/- 2std. parameter space and calculates the min and max bounds for the resulting impedance.
I also added a plotting method (see plottingExample.ipynb) since I agree that this is the most natural venue to think about confidence intervals. Definitely still rough around the edges and we could use to open more of the plotting, CI calculation variables, etc. as optional parameters, but I think we're headed in the right direction.
We should return confidence intervals on our parameter fits (probably as a model.confidence_ attribute). The standard deviation can be calculated by taking the square root of the diagonal elements in the covariance matrix that is returned by leastsq (
np.sqrt(np.diag(pcov)
).It would also be awesome if the predict method could predict the upper and lower confidence interval ranges too!
The text was updated successfully, but these errors were encountered: