-
Notifications
You must be signed in to change notification settings - Fork 116
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
CADD-SV plugin not working #667
Comments
Hello @kittysher , Thanks for your query! I can confirm that I can re-produce the issue. We are looking more into it and let you know once we have more information. Best regards, |
Hi @kittysher, Thanks for your patience. Here is why your data is not getting annotated - Looking more at you input file -
Hope it helps answer your question. Let me know if you have any further query. Best regards |
Hi Nakib, Thank you for getting back to me about this issue. Many thanks |
Hello @kittysher, Yes, that is the case. That is why you will see the breakend variant getting annotated in the output with things such as transcript affected and consequence on that transcript -
But annotation from CADD plugin is different matter. Plugins are extension to Ensembl VEP and often depends on files from external resources. As I pointed out CADD annotation file (which is an external resource) currently supports
You can learn more about Ensembl VEP plugins from here - https://www.ensembl.org/info/docs/tools/vep/script/vep_plugins.html Best regards, |
Hi Nakib, OK thank you for clarifying the difference between the VEP and CADD annotations. WARNING:` Plugin 'CADD' went wrong: Many thanks |
Hi @kittysher, The warning is given when the alternate allele type is not supported. In the example you provided it was the It could be there are no variants in your input files that gets matched with CADD SV file that are of supported types. Can you provide any other variants that is not annotated but should be? Best regards, |
Hello @kittysher, Best regards, |
Hello,
I am trying to run the CADD-SV plugin on my consensus SV vcfs which have already been generated. They have been labelled with VEP already but I am trying to add in the CADD information too. I am using VEP v110 and the input vcfs are v4.2 Here is an example of the variants I am trying to annotate:
My VEP script is this:
The VEP command runs but I get an error about the CADD plugin, and the CADD fields in the output are all missing:
WARNING:` Plugin 'CADD' went wrong:
-------------------- EXCEPTION --------------------
MSG: Missing reference or alternate sequence
I am very stuck as to what is going wrong - is this due to incompatibility between the VCF versions? Please could you help me to get this plugin up and running?
Thank you very much,
Kitty
The text was updated successfully, but these errors were encountered: