Automatically add channels for LIME if the input is greyscale #215
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
egpbos
approved these changes
Feb 10, 2022
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.
Even if the input is greyscale, like MNIST, LIME still requires 3 channels. The preprocessing function was our workaround to handle this, but it is unclear to the user because LIME adds a batch axis, before the preprocessing function is called.
This PR adds functionality to automatically add/remove the extra channels for LIME.
I'm not too happy about the
_get_full_preprocess_functionmethod, but I couldn't find a better way yet without assigning lambda expressions, which the linter doesn't allow.