-
Notifications
You must be signed in to change notification settings - Fork 55
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
Running SVTyper on any SV tool #85
Comments
I have also tried running |
Hi Molly, |
I think there is likely to be a version of svtyper that does this at some point, but I'm not sure when that may happen. I've run into the same issue for Manta and have had to add CIPOS and CIEND manually using bcftools. |
Ok, thank you for the update! |
I know this is an old issue, but is there a standardised way to decide how to bound CIPOS and CIEND? Is it a proportion of the overall size of the SV? |
#111 works around the missing CIPOS |
Dear @ernfrid I know this is a very old issue; but may I ask how you added CIPOS and CIEND using bcftools? Any specific commands? Can bcftools calculate these CIs for SVs? Thank you in advance |
@dr-ashu-geno - It's been too long for me to recall for certain, but I'm fairly sure I calculated outside of svtools and then simply added the new tags to the VCF using |
Hi,
I'm hoping to be able to run SVTyper in a generic mode on any SV tool.
I have tried running SVTyper on Manta and SvAbA vcfs, and am running into errors because SVTyper is looking for information that is not listed in these files. For example, some entries in Manta do not have CIPOS and SvAbA does not list CIPOS for any of its entries. SVTyper stops and throws an error because it cannot find CIPOS. There have also been other format-specific errors I've run into, such as SVTyper throwing an error when an additional '>' is found in the FORMAT header section.
Will there be a version of SVTyper that is more lenient with the vcf format, so that it can be run on other SV callers besides Lumpy?
The text was updated successfully, but these errors were encountered: