Asymmetric Shapley values#474
Draft
LHBO wants to merge 2 commits into
Draft
Conversation
…n that computes the correct asymmetric weight functions. I might contain some logical errors.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Started investigating the asymmetric problems.
Implemented a function
weight_matrix_permutation()that takes in the causal order and outputs the weight matrixWwhich we should have used to compute the Shapley values in the asymmetric setting. It might contain some edge case logical errors, but it gives what I got by hand for some small scenarios.Compared how the Shapley values look for the Bike dataset when we use this new weight matrix, and we got some minor changes in the Shapley values, but no huge changes.