-
Notifications
You must be signed in to change notification settings - Fork 597
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
Funcotator - Problems with variant alleles that span exon, coding sequence start/end boundaries #4307
Comments
A temporary fix is in that will only annotate variants as in a CDS if they are contained within that CDS. |
This is related to #4804 |
Can oncotator handle this? |
Funcotator and Oncotator both produce the same results for |
|
This is related to #3749 |
For the following variants:
VEP seems to produce incorrect data:
There is no cDNA string / amino acid change and the positions have Oncotator seems to produce incorrect data:
The protein change / cdna string / coding string fields are all incorrect. The positions in the transcript may also be incorrect. |
Note that this ticket also applies to variants that span between the UTR and flanking regions. |
The way start positions are calculated causes issues when alleles span the boundaries of exons and the coding sequence itself.
For exon boundaries:
The error stems from
FuncotatorUtils::getStartPositionInCodingSequence
and how the results of that method call are used in theGencodeFuncotationFactory
.In addition:
Funcotator must be able to handle indels that span exon start boundaries.
For example, in hg19 the following variant is not handled properly:
chr5:71622537-71622538 CA->C
The current workaround is to throw a FuncotatorUtils.TranscriptCodingSequenceException for the transcript causing this problem in Gencode.
For Coding sequence boundaries, the following variant in hg38 causes a problem:
The text was updated successfully, but these errors were encountered: