-
Notifications
You must be signed in to change notification settings - Fork 48
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
No TP-base and TP-call match in the benchmark results #132
Comments
The
I was able to see:
Truvari uses pysam to parse VCF files and while there are safe guards for
|
Sorry, one more thing... The |
Thanks, I followed the step you mentioned and it worked. |
Hi,
Thanks to the efforts of authors in providing this tool Truvari. We had problems comparing two vcf files using Truvari V3.4.0.
Running :
truvari bench -b GM12878.chr21_14_19M.true.v1.vcf.gz -c lra.chr21.14-19_wr.v1.vcf.gz -o ./out_lra -r 1000 --giabreport -p 0.00
The truvari result shows that TP-base and TP-call are both 0, and got an error
KeyError: 'sizecat'
:But we did find match insertion and deletion results from IGV visualization of the two vcf, for example, the chr21-16359642-DEL-139 in base VCF / chr21-16359640-cuteSV.DEL.6 in comparison VCF , and the chr21-18251499-INS-448 in base VCF / chr21-18251502-cuteSV.INS.8 in comparison VCF;
In addition, we used usable_vcf tool to verify these two VCF files, and got VCF validation failure:
I have attached the base VCF and compression VCF to this issue. If it is the VCF file format problem? Or any other problems, could you give us some help? thank you!
GM12878.chr21_14_19M.true.v1.vcf.gz
lra.chr21.14-19_wr.v1.vcf.gz
The text was updated successfully, but these errors were encountered: