-
Notifications
You must be signed in to change notification settings - Fork 91
954 prediction explanations doc #981
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…elines/explanations.
…es to _explain_prediction.
…ing section on SHAP to model_understanding tutorial.
Codecov Report
@@ Coverage Diff @@
## main #981 +/- ##
=======================================
Coverage 99.85% 99.85%
=======================================
Files 178 179 +1
Lines 9282 9283 +1
=======================================
+ Hits 9269 9270 +1
Misses 13 13
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well-explained! LGTM :D
Not blocking but do we need the evalml/tests/pipeline_tests/explanations_tests/__init__.py
empty file?
@angela97lin Thanks! Good point, I'll delete in this PR! |
"\n", | ||
"In the example below, we explain the prediction for the third data point in the data set. We see that the `worst concave points` feature increased the estimated probability that the tumor is malignant by 20% while the `worst radius` feature decreased the probability the tumor is malignant by 5%.\n", | ||
"\n", | ||
"The interpretation of the table is the same for regression problems - but the SHAP value now corresponds to the change in the estimated value of the dependent variable rather than a change in probability. For multiclass classification problems, a table will be output for each possible class." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@freddyaboulton I just checked this out. This looks great! My only thought was this paragraph could go after the example since its not directly connected to the example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Description
Fixes #954 by adding
explain_prediction
to the api reference and by adding example usage to the Model Understanding tutorial in the user guide.Docs Change
After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of
docs/source/release_notes.rst
to include this pull request by adding :pr:123
.