-
Notifications
You must be signed in to change notification settings - Fork 151
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
VEP112 predicts "inframe_insertion, stop_retained_variant" in cases where previously was predicted as "frameshift_variant, stop_gained" #1710
Comments
Hi @jperales, Thanks for reporting this case. What do you think it would be the expected consequences for this example? If you have more cases like so, please send us so we can take a look at them and see how they behave. Cheers, |
Regarding the consequence of the example above, it looks the expected consequence would be an The reference CCDS sequence data for that transcript would be (source: https://www.ncbi.nlm.nih.gov/CCDS/CcdsBrowse.cgi?REQUEST=CCDS&DATA=CCDS46852 , 2847 nt , 948 aa):
If we insert the variant in the transcript, the sequence changes as follows. Please note that it leads to a frameshift and stop gained codon TAA (denoted as '-'):
I have only found another example affected by this issue: Thank you very much for the efforts on this and your great work! |
Hi Javier, Thank you for sending those examples. :) I will go through them with my team and see how we can improve VEP based on them. Cheers, |
Hi @nuno-agostinho , Moreover, I realized that the issue is only with the consequence term Please note that the correct prediction of a Thanks you very much! |
Hi @nuno-agostinho , Best, |
Hi @jperales, The issue is indeed a bug and occurs when the first amino acid is identical between the reference and alternative peptide sequences (and there is a stop insertion in the alternative sequence, We aim to have a bug fix in place for the next version of VEP (113). Sorry for the inconvenience. Best, |
Hi @olaaustine , Best, |
Hi @jperales, |
I noticed that VEP 112 predicts an opposite consequence as compared to previous versions for certain insertions (rare cases). It predicts
inframe_insertion,stop_retained_variant
in cases whereframeshift_variant,stop_gained
was predicted before. Notably, these affect protein coding transcripts on exons, and the insertion length is not divisible by 3, so I would expect the frameshift. Moreover, I doubt whetherstop_retained_variant
makes sense in the region as I have seen this happening near splicing donor sites of first exons of protein coding transcripts, hence I would not expect a stop codon in the region. See below for 1 example case. Thank you!Example case:
Variant:
3:56591278-56591278 T>TGGGGTAAGCA
. It would be a 10-bp insertion on CCDC66 gene. Let's focus on the canonical transcriptENST00000394672
. Then this variant would affect the last part of the 1st exon, almost at the splicing site.VEP command line for VEP 111 & its output
VEP command line for VEP 112 & its output
System
Full error message
None
Data files (if applicable)
They include:
NOTE: Beyond that example, I can provide a more complete list of cases found upon request
The text was updated successfully, but these errors were encountered: