-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Score of the surrogate model #452
Comments
@garyee great point. It's already possible to get the replication score here:
However this needs to be turned into a public API and integrated with our explanation and dashboard, so it's always shown for explanations from mimic explainer. |
@garyee , how do you plan to use this score? Like comparing the various surrogate models used with MimicExplainer? If that is the case, could you try the above private function to see if this helps your scenario? As Ilya mentioned we could turn this into a public function and add to an interpret notebook. Regards, |
@gaugup , that would be a possible scenario. I would like to get the score to know how good the explanations of the surrogate model are ... how close the surrogate model is to the underlying "black box" model. @imatiach-msft I did not catch that method there. It would be great if it could be exposed. |
Hi! has the function been used in any of the notebooks yet? :) |
@SamiurRahman1, @garyee , there a new notebook in the PR #506 which uses the above function. If you plan to use the notebook in the PR, then do let us know if you would want to add anything to the notebook. Regards, |
Is your feature request related to a problem? Please describe.
Is there a way to compute a score (like R-squared) for the output of the surrogate model?
I would like to know if I can trust the explanations given by the surrogate or if I should be careful.
Describe the solution you'd like
It would be great if there would be a score property in GlobalExplanation and a parameter when creating the explainer to pass in a custom score function.
The text was updated successfully, but these errors were encountered: