adding plugin parameter to vcf2maf #357
Open
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
Adding parameters to support use of plugins
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.
Hi @ckandoth , I needed to be able to run the AlphaMissense VEP plugin in vcf2maf, so I made a couple of small modifications to enable vcf2maf users to pass plugin instructions to VEP's --plugin parameter. Candidly, I've only tested this with the AlphaMissense plugin, so I am not sure if it works with any other or all VEP plugins, but I imagine it should work with any of them unless they're doing something odd to the VCF file and not just adding annotations.
Curious if you would be interested in adding this to the next vcf2maf release? Thanks!
Happy to hear any feedback or suggestions you might have as well.