-
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
Should the Downstream plugin predict stop_lost downstream sequences #286
Comments
Hi I am looking into the downstream sequence for frameshift,stop_lost variants. Please could you let me know which version of VEP you are using and the vep command being used with the Downstream plugin. Thanks |
It looks like the particular VCF I'm looking at is a bit older and was annotated with VEP 84. Here is the VEP header: |
Hi Are you running VEP in offline mode (using the flag --offline)? If VEP is run in offline mode using the flag --offline, a FASTA file is required to get the sequences for the 3' UTR. Sequence may be incomplete without a FASTA file or database connection I have updated the documentation for the plugin for future releases. Thank you for flagging this issue. Helen |
Hi Helen, I've been testing the downstream plugin with stop lost variants with Susanna and it seems like with the following command options I still fail to obtain a downstream sequence:
The example variant I'm looking at is : Thanks. |
Hi Are you getting any information returned on the change in length relative to the reference protein? The Downstream plug returns 2 fields When I ran VEP with the Downstream plugin for your example variant the Location chr1:212360769 Are you getting a value returned for ProteinLengthChange? There is no downstream protein as the downstream sequence start with 'A' and result is a stop codon. To test the Downstream plugin is returning sequence, an example variant to use is Location 19:643601-643602 Regards |
Hi Helen, Thank you for looking into this. We confirmed that the example variant results in the expected DownstreamProtein sequence. We also identified a few similar variants in our VCFs so we think we have our VEP commands working correctly now. A more general question for the VEP Consequence annotation would be whether variants that result in basically "replacing" the stop codon should have a Consequence of |
I'm glad to hear that you've got your VEP commands working correctly. Regarding your more general question of when we assign stop_lost: http://www.sequenceontology.org/browser/current_release/term/SO:0001578 - "A sequence variant where at least one base of the terminator codon (stop) is changed, resulting in an elongated transcript." So the consequence we assign depends on where a theoretical new-stop-codon is positioned. With the release of Ensembl 100 (officially released this afternoon), we have introduced the option If you have any other issues or if there's anything else we can do to help, please feel free to get in touch. Kind Regards, |
Hi @aparton, Sorry to bother you about this again. We thought we had it fixed but we're still seeing some odd behavior. We are not seeing any XXXs in the DownstreamProtein field anymore, but we are also not seeing any downstream sequence predictions if the variant is
This is a TAG mutated to a TAT which codes for tyrosine and not a new stop codon so I would expect a DownstreamProtein prediction. We also aren't seeing any values for the ProteinLengthChange for the The CSQ header is
and the VEP command we ran is
|
The Downstream plugin predicts the downstream effects of a frameshift variant on the protein https://www.ensembl.org/info/docs/tools/vep/script/vep_plugins.html#downstream Regards |
Is there a supported plugin for this use case? |
There is not a supported plugin for this use case. I will discuss with the team if this functionality can be included in a Plugin. However may only be a functionality in the longer term. Regards |
Your request for including stop_lost was added to our work list for investigation. I will close off this ticket, but we will contact you if we do make this change. Please feel free to reopen the ticket or open a new one if you have further questions. Regards |
Right now it appears that the Downstream plugin doesn't output a predicted downstream sequence for
stop_lost
variants (or it is just a sequence of multipleX
s). Is this the expected behavior? Would it be possible to add this feature?The text was updated successfully, but these errors were encountered: