-
Notifications
You must be signed in to change notification settings - Fork 11
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
expose variant filtering params up to immuno #97
Comments
I would like to be able to do this in my immuno YAML:
But currently I think I can only do the varscan one? |
Some notes on this issue:
The only real application I can see to having separate variables for varscan and fp_filter is where you set the varscan_filter at a more stringent threshold (e.g. 0.1) but then apply a more relaxed filter in fp_filter (e.g. 0.05). This would allow lower VAF variants to come from Strelka/Mutect than that allowed from VarScan. I'm not entirely convinced that this narrow use case is worth the complexity it creates to have separate variables. However, it does seem that was the intent of how the pipeline was created. I am experimenting with a PR that will implement the following approach:
|
This now complete (#136) and working as expected. |
It seems that currently I can't configure these values in my YAML?
Tumor VAF cutoff applied to individual variant caller results (mutect and strelka) prior to creating a merged VCF
analysis-wdls/definitions/tools/fp_filter.wdl
Line 14 in 7d0c18d
LLR threshold applied to the merge VCF
analysis-wdls/definitions/detect_variants.wdl
Line 67 in 7d0c18d
The text was updated successfully, but these errors were encountered: