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.

Sign up for GitHub

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

Jump to bottom

Missing `svdb_origin` SV vcf tag leads to bad caller info for merged variants in scout #244

Open

alkc opened this issue Oct 28, 2024 · 0 comments · May be fixed by #245

Open

Missing `svdb_origin` SV vcf tag leads to bad caller info for merged variants in scout #244

alkc opened this issue Oct 28, 2024 · 0 comments · May be fixed by #245

Contributor

alkc commented Oct 28, 2024

The GT call info for SVs marged in svdb looks like this in scout, with Pass tags for non-existent or wrong callers:

scout looks for caller info in two places in VCF INFO, one of which is svdb_origin which is added by SVDB 2.6 and up (we run 2.2?)

The text was updated successfully, but these errors were encountered:

alkc linked a pull request

that will close this issue

Update SVDB to 2.8.2 #245

Draft

36 tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment