381 override annotation keys#388
Merged
Merged
Conversation
* Allow model to run on alternative set of VCF keys to allow for inference pipeline refactoring flexibilty. * Allow user-defined explainabilty threshold Signed-off-by: Tor Björgen <tor.bjorgen@scilifelab.se>
torbjorgen
force-pushed
the
381-override-annotation-keys
branch
from
a2a49d5 to
94d1b7a
Compare
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.
Allow user to override model default input key names in VCF,
so that it can allow for some flexibility in refactoring
the pipeline where it's running.