Skip to content
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

Slivar for SVtyper vcf #92

Closed
nroak opened this issue May 25, 2021 · 3 comments
Closed

Slivar for SVtyper vcf #92

nroak opened this issue May 25, 2021 · 3 comments

Comments

@nroak
Copy link

nroak commented May 25, 2021

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?

~/resources/slivar/slivar expr \
--vcf ../SVTYPER.perSample.cohort.merged.ann.snpeff.ann.vcf \
--pass-only \
--out-vcf $family.segregating.vcf \
--js functions.js \
--ped $family.ped \
--info "INFO.SVLEN >100" \
--family-expr "shared_affected:fam.every(affected_any)" \
--family-expr "shared_affected_only:fam.every(affected_only)" \
--family-expr "het:fam.every(function(s) {return s.het == s.affected && s.hom_ref == !s.affected})" \
--family-expr "hom_alt:fam.every(function(s) {return s.hom_alt == s.affected && s.hom_ref == !s.affected})" \
--family-expr "seg_dom:fam.every(segregating_dominant)" \
--family-expr "seg_rec:fam.every(segregating_recessive)"

> slivar version: 0.1.13 8cf3a240d38c05d14d4208a6c074aca89332519f
[slivar] 132 samples matched in VCF and PED to be evaluated
error: unknown impact "feature_fusion" from csq "N[CHR15:101980258[|feature_fusion|LOW|||transcript|ENST00000456328.2|processed_transcript||t(1%3B15)(p36.33%3Bq26.3)(n.-1391)||||||" please report the variant at https://github.com/brentp/slivar/issues

@brentp
Copy link
Owner

brentp commented May 25, 2021

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.

@brentp
Copy link
Owner

brentp commented May 25, 2021

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.

@brentp brentp closed this as completed in e6a75f1 May 25, 2021
@brentp
Copy link
Owner

brentp commented May 25, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants