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

[User Story] Add more SV databases for frequency filtering #1442

Open
3 tasks
mathiasbio opened this issue May 29, 2024 · 0 comments
Open
3 tasks

[User Story] Add more SV databases for frequency filtering #1442

mathiasbio opened this issue May 29, 2024 · 0 comments
Labels
User-Story A User-Story describing new functionality

Comments

@mathiasbio
Copy link
Collaborator

mathiasbio commented May 29, 2024

Need

As a clinician I want true somatic variants, even when doing tumor only analyses without a matched normal.

Currently SV filtering is done with the swegen database and the locally built database of germline calls from the rare-disease pipeline. However these databases are likely not exhaustive and it could be beneficial to add more databases. In this article https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9047340/ they describe using several additional databases for SV filtering:

For population frequency-based filtering, we considered the variants occurring in more than 1% of the population as common. SVs called in the VCF file are removed from the analysis if they show greater than 80% reciprocal overlap with a common variant in any of the source databases (DGV, gnomAD-SV, dbSNP, and HGSVC SVs).

We should add these and see if they are useful in our filtering as well. In short, they mentioned these databases:

DGV: http://dgv.tcag.ca/dgv/app/home
gnomAD-SV: https://gnomad.broadinstitute.org/news/2019-03-structural-variants-in-gnomad/
HGSVC SVs: https://www.internationalgenome.org/data-portal/data-collection/structural-variation

And dbSNP (though I cannot find what they used)

Suggested approach

No response

Considered alternatives

No response

Deviation

No response

System requirements assessed

  • Yes, I have reviewed the system requirements

Requirements affected by this story

No response

Risk assessment needed

  • Needed
  • Not needed

Risk assessment

No response

SOUPs

No response

Can be closed when

No response

Blockers

No response

Anything else?

No response

@mathiasbio mathiasbio added the User-Story A User-Story describing new functionality label May 29, 2024
@github-project-automation github-project-automation bot moved this to Todo in BALSAMIC May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
User-Story A User-Story describing new functionality
Projects
Status: Todo
Development

No branches or pull requests

1 participant