issue #192: decouple visualisation from core explainability #203
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
christinaexyou
force-pushed
the
issue-192
branch
5 times, most recently
from
4d3f128 to
0e95b69
Compare
christinaexyou
force-pushed
the
issue-192
branch
4 times, most recently
from
5e7a6fe to
b42beca
Compare
|
changes made:
|
ruivieira
approved these changes
Mar 6, 2024
christinaexyou
force-pushed
the
issue-192
branch
from
b42beca to
a8b3b8f
Compare
|
changes made:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR address #192 by moving viz methods from the
explainersmodule to following files:visualizations/visualization_results.py: abstract class for visualization methodsvisualizations/factory.py: gets visualization according to explanation method/classvisualizations/shap.pyvisualizations/lime.pyvisualizations/pdp.pyvisualizations/distance.py