-
Notifications
You must be signed in to change notification settings - Fork 516
validate forward_fun output shape in FeatureAblation #1091
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
Closed
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -345,17 +345,6 @@ def forward_func(inp): | |
with self.assertRaises(AssertionError): | ||
_ = ablation.attribute(inp, perturbations_per_eval=2) | ||
|
||
def test_error_agg_mode_incorrect_fm(self) -> None: | ||
def forward_func(inp): | ||
return inp[0].unsqueeze(0) | ||
|
||
inp = torch.tensor([[1, 2, 3], [4, 5, 6]]) | ||
mask = torch.tensor([[0, 1, 2], [0, 0, 1]]) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This test checks when rowwise |
||
|
||
ablation = FeatureAblation(forward_func) | ||
with self.assertRaises(AssertionError): | ||
_ = ablation.attribute(inp, perturbations_per_eval=1, feature_mask=mask) | ||
|
||
def test_empty_sparse_features(self) -> None: | ||
ablation_algo = FeatureAblation(BasicModelWithSparseInputs()) | ||
inp1 = torch.tensor([[1.0, -2.0, 3.0], [2.0, -1.0, 3.0]]) | ||
|
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.
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.
I think in future we can be more strict here by requiring the 1st dim of output to be the same as input batch size, instead of just require it "grow with the input batch size".
For example, if the input batch is
2
, the output's 1st dim can be2
,4
, or7
; currently it will be OKwhen we expand the input batch size to
4
, the output's 1st dim becomes4
,8
, or14
respectively.But the last 2 cases are pretty weird and unlikely to happen. It may be easier to always require output's 1st dim to be batch size and it must be the same as input batch size in this "non-aggregation mode". So if the input batch is
2
, the output's 1 dim must be2
ifperturbations_per_eval > 1
cc @vivekmig @NarineK