Display VCF filters as QC bages in scout cancer
See original GitHub issueI was going to add the annotated VCF filters as badges for the cancer variants list view.
Scout stores these flags as “filters” in the database and are included in the variant_obj
.
We would like to apply different formatting to these flags in a way that would be extendable and meaningful for different sites. I was therefore thinking of storing the configuration in the scout database, much like how we do with the dismissal terms.
What do you think?
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Structural Variant Analysis - Cancer Genomics Workshop
Be able to filter high confidence SV predictions. Have gained basic knowledge to interpret the VCF output provided by DELLY.
Read more >COSMIC Data Analyses
Variants presented in the vcf files have been screened by a series of post processing filters which flag likely false positive calls based...
Read more >Clinical-Genomics/scout: New documentation links and ... - Zenodo
logo-display.png 46.0 kB; logo.sketch 28.8 kB; scout-variant-demo.png 310.2 kB ... cytoband.py 2.1 kB; event.py 15.5 kB; filter.py 4.6 kB; hgnc.py 15.3 kB ...
Read more >vcfView: An Extensible Data Visualization and Quality ... - NCBI
We present vcfView, an interactive tool designed to support the evaluation of somatic mutation calls from cancer sequencing data. The tool takes ...
Read more >aSh - River Thames Conditions - Environment Agency - GOV.UK
Biografia de rosy morfe, Hamulce rowerowe wiki, Open drawing pad, ... Bio donald o connor, White magic book amazon, Uganda cancer institute. H7gogogo....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Wouldnt that soon become bloated and hard to manage? Especially if different sites are to have different prefixes. Then it would be better to let the formatting be defined in the config.py or to load the configuration into the database.
Not having these in the constants file doesn’t mean that there are no defaults. We could either have a defaults json file which are being loaded when the database is being setup (just like the evaluation terms), or just have a default dictionary in the config file.
I do think we should strive to unify as much as possible but it seems to me that is a process that takes a lot of time to mature.