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

Clarification on derivation of SV length and type #210

Open
olivia-gc opened this issue Mar 7, 2024 · 0 comments
Open

Clarification on derivation of SV length and type #210

olivia-gc opened this issue Mar 7, 2024 · 0 comments

Comments

@olivia-gc
Copy link

Hi, I am trying to understand how SURVIVOR filters and merges vcfs from different callers.

I just wanted to confirm that SURVIVOR tests multiple strategies to derive SV length depending on the type and caller.
For ex: END - POS2 (instead of END - POS) for TRAs when SVLEN is not available.

I also wanted clarification on dealing with BNDs during merge. From my understanding, SURVIVOR will type BNDs to INV or TRA.
With this, if I have vcfs for a sample that are separated by SV type, should I be merging INV vcfs from one caller with BND vcfs from another to see if there is a consensus call set between them?

Thank you very much for your help

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

1 participant