Fix MultiDimensional attribution aggregation
#292
Merged
Conversation
This file contains 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
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.
Description
This PR fixes the issue highlighted in #291 in which the information contained in configuration attributes (preceded by
_) inFeatureAttributionSequenceOutputclasses was not copied over after callingout.aggregate. This was causing methods likevalue_zeroingto break, since the defaultMultiDimensionalFeatureAttributionSequenceOutputoutput was assumed to be 4-dimensional from theattentionmethod.In the updated version, a new property
configwas added toFeatureAttributionSequenceOutputto easily access all configuration attributes, and the resulting properties are now updated correctly.