Refactor XAIBase interface #20
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
adrhill
force-pushed
the
ah/update-interface
branch
from
caf21c7
to
bfe457d
Compare
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.
Closes #18, #19.
This refactor of the XAIBase interface aims to make the Julia-XAI ecosystem more compatibile with @pat-alt's Taija ecosystem and to support a wider range of NLP models (Julia-XAI/ExplainableAI.jl#164)
It includes a bunch of breaking changes:
inputfield toExplanationstructanalyzetoAbstractArrayinputsanalyzekeyword-argumentadd_batch_dim, which made the assumption of array inputscall_analyzermethod instead of making the analyzer struct callable. This helps with type stability, which is now tested with JET.jl.@pat-alt is there anything else that would be useful for Taija?