-
Notifications
You must be signed in to change notification settings - Fork 6
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
Post-proces SURVIVOR output with vcf2bedpe.R #82
Comments
I will update the workflow (related to #68). |
StructuralVariantAnnotation (SVA) package supports the following VCF notations:
Currently, we use the two notations (BND for TRA/CTX?) in the workflow. |
SVA supports non-compliant VCFs:
Is it correct to say that vcf2bedpe.R script (and bedpe2vcf.py) is needed to handle also LUMPY and SURVIVOR output? |
Yes. I miss the inversions (INV) in the SVA documentation. Based on my tests SVA supports also INV (see page 3 of VCF specs). |
True. Nevertheless, INVs are handled, for example, in vcf2bedpe.R, |
The script is used to process Manta, DELLY, LUMPY, GRIDSS and SURVIVOR VCF files. However, the following lines do not make it clear for the latter (e.g., TRA vs. CTX). sv-channels/scripts/R/vcf2bedpe.R Line 14 in 50b1a55
sv-channels/scripts/R/vcf2bedpe.R Line 52 in 50b1a55
sv-channels/scripts/R/vcf2bedpe.R Line 71 in 50b1a55
sv-channels/scripts/R/vcf2bedpe.R Lines 95 to 96 in 50b1a55
Moreover, all issues reported here should be handled by this script. Correct? |
In this workflow, vcf2bedpe.R is only used to convert SV callers' output. According to GooglingTheCancerGenome/sv-gen#43, we also need to post-process SURVIVOR simSV output but this script seems missing in the workflow.
The text was updated successfully, but these errors were encountered: