Closed nroak closed 3 years ago
Hi, you certainly should be able to use slivar for SVs.
I'll add this to the default-order list, but meanwhile, you can download this file: https://raw.githubusercontent.com/brentp/slivar/master/src/slivarpkg/default-order.txt
and add "feature_fusion" somewhere toward the bottom (if you agree that it's low impact) and save that.
Then if you export the environment variable: SLIVAR_IMPACTFUL_ORDER=/path/to/your/saved-impact-order.txt
, slivar will use that instead of the default.
And if you're not already, note that duphold annotations work well to filter variants and you can add expressions for that to the slivar command.
I added feature_fusion
to that file so now you just need to download it and set the environment variable to the path where you keep it.
I'm using Slivar to apply segregation filters to a multi-sample vcf for SV calls generated by SURVIVOR followed by SVTYPER. I understand that Slivar was mainly developed through SNV/InDel point of view, so the SV variant classes won't be supported. That said, I have had good success with GT field based filtering for segregating SVs.
However, the output generates errors like below for nearly 2.5mil entries in the VCF: Is there any way to silence these messages that we would expect for non-SNV calls?