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
vep give different result when using multi-thread(--fork).
problem:
Some gene(like ENSG00000169047 or ENSG00000168769) will loss its refseq HGNC ID(near field EntrezGene) when using --fork, and they are shown in single-thread result.
Additional information
This inconsistent is due to the thread setting, same threads give same results bewteen different running, but different threads setting lead to different result.
I believe this is a multi-thread inconsistent bug. And I think this bug happens widely, Any WES vcf and VEP merged cache can reproduce the problem, no specific inputs need.
Hi @karlestira,
Unfortunately I am not able to reproduce this issue on my end. Is there a specific test input file that can be shared to help us debug this?
Hi @karlestira, Unfortunately I am not able to reproduce this issue on my end. Is there a specific test input file that can be shared to help us debug this?
Kind regards, Likhitha
vcf is from vardict, and some pre-process has been done.
In my system, the diff is between line 62(the cmd line, it is no problem), 4892, 4893, 4987, 4988(these 4 lines is different in HGNC ID when transcript is from refseq)
Describe the issue
vep give different result when using multi-thread(--fork).
problem:
Some gene(like ENSG00000169047 or ENSG00000168769) will loss its refseq HGNC ID(near field EntrezGene) when using --fork, and they are shown in single-thread result.
Additional information
This inconsistent is due to the thread setting, same threads give same results bewteen different running, but different threads setting lead to different result.
I believe this is a multi-thread inconsistent bug. And I think this bug happens widely, Any WES vcf and VEP merged cache can reproduce the problem, no specific inputs need.
System
Full VEP command line
Full error message
No error message.
The text was updated successfully, but these errors were encountered: