You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I tested using version 113 of VEP. Small VCF files work fine, but when I provide a larger VCF file with about 100,000 lines, the program is interrupted, showing numerous warnings: WARNING: “Transcript-assembly mismatch”.
我的命令行是:
Hi @GSYongWu,
This warning should not stop the VEP run. Is the output truncated?
This warning is thrown when there is an allele mismatch between the RefSeq and the Ensembl transcript at that specific location.
I can see from your command you run the two options:
--refseq
--use_given_ref
Running the option --use_given_ref should not throw this warning however there is an issue with this option in release 113.
Can you please send an example of your output file? For example the output for 1_144994660_C/A.
Hi @dglemos
Yesterday, I ran the process several times, and it terminated each time. The message before termination was: "ensembl-vep-release-113.0/Bio/EnsEMBL/Variation/Utils/VariationEffect.pm line 936.
Died in forked process 74883”
Today, I reran it, and the result had only warnings and did not terminate.
The locus result file 1_144994660_C/A is here: 1_144994660_C-A.vep.zip
Thanks for providing the data.
The variant output looks correct.
If you run vep with option --use_given_ref you can ignore the warning WARNING: Transcript-assembly mismatch in <>. This warning indicates the alleles don't match at this position between RefSeq and Ensembl, but as you are running the option to use the input allele this mismatch won't be a problem for your job.
We are working on fixing this warning.
Hi,
I tested using version 113 of VEP. Small VCF files work fine, but when I provide a larger VCF file with about 100,000 lines, the program is interrupted, showing numerous warnings: WARNING: “Transcript-assembly mismatch”.
我的命令行是:
The WARNING for example:
The text was updated successfully, but these errors were encountered: