Closed phu5ion closed 5 years ago
Sorry about the issue and thanks for the report. Would you be able to share your input YAML file to understand better how you're running scalpel? Is it possible you're trying to run it as a standalone caller, like this issue:
https://github.com/bcbio/bcbio-nextgen/issues/1586
In general we haven't done a ton of work on scalpel recently and might also be able to offer alternative suggestions for callers with an understanding of your use case. Hope this helps.
Hi Brad,
Sure.
details:
- algorithm:
aligner: bwa
mark_duplicates: true
recalibrate: gatk
realign: gatk
coverage: /home/dlho/references/bedfiles/Cancer216-full-targets_hg38.bed
variantcaller: [mutect, varscan, freebayes]
indelcaller: scalpel
svcaller: [lumpy, manta, cnvkit]
svprioritize: /home/dlho/references/bedfiles/Cancer216-full-targets.list
effects: vep
effects_transcripts: canonical
save_diskspace: true
tools_off: [gemini, gatk4]
analysis: variant2
genome_build: hg38
I'm running scalpel as an indel caller in addition to Mutect, so as to call both snvs and indels. I'm open to using Mutect2 as an alternative since it does the same by itself too, but was wondering about its performance vs Mutect. Would appreciate any advice you have about this issue, thanks!
Hi,
I was wondering how's the issue on the problems with scalpel described above?
As a side, I'm running Mutect2 and not too happy with the default settings. May I know how to change them? Specifically I'll like to change this argument because Mutect2 is missing out real variants:
max_alt_alleles_in_normal_count=1
Thanks!
Thanks for the additional details. That all looks good in terms of scalpel usage so I'm not sure why it's generating an incorrect header without the REJECT filter tag. If you'd be able to supply a small example that does this we could try to reproduce and fix.
Alternatively, I'd suggest trying to substitute in vardict
and strelka2
in place of using scalpel
for indel calling. Both have nice indel sensitivity for somatic calling and can avoid the issue entirely.
For MuTect2, you can tweak and add other options by specifying them in the resources (https://bcbio-nextgen.readthedocs.io/en/latest/contents/configuration.html#sample-or-run-specific-resources)
resources:
mutect2:
options: []
We'd have a lot of interest in hearing out your experiences tweaking MuTect2. We've also been discussing in #2357 with regards to tumor-only calling so welcome hearing what works well for your samples. Thanks again for all the work debugging and hope this helps.
Thanks, closing this out-- there is a reasonable workaround suggested which should solve it. The Mutect2 issue is being discussed in #2357 so that will probably be the issue to talk about this stuff going forward.
Hi,
Sorry for opening another issue. It looks like there is something wrong with either bcftools command or the header of scalpel vcf files:
This is what the header of the problematic file looks like:
Just some thoughts, but I was wondering whether the problem is as described in the error message, and it's because the info field "REJECT" is not defined in the header. Could anyone help pls? Thanks!