Closed sci-kai closed 2 weeks ago
I had a similar issue on 3.4.1, where it gave me an error about not having a tumor-sample
which was required by mutect2
, I added all the possible columns (icluding sex) and it fixed the bug, it might not be parsing the sample table properly. Try with that and see if it fixes it for you. It is a different error, once I am back on my rig I can update this with the error log.
Has this been resolved?
I have an almost identical issue, also starting with variant calling from aligned bam files, and Mutect2 is also complaining that a sample isn't in the bam header. Has anyone been able to resolve this?
My samplesheet contains patient,sex,status,sample,bam,bai
Hi, so I could resolve this error as following:
The problem here is the mismatch between the sample names in the BAM header (when starting with BAM files) and the sample names specified in the mutect2 parameters defined in conf/modules/mutect2.config
.
conf/modules/mutect2.config
contains in the process scope:
withName: 'MUTECT2_PAIRED' {
ext.args = { params.ignore_soft_clipped_bases ?
"--dont-use-soft-clipped-bases true --f1r2-tar-gz ${task.ext.prefix}.f1r2.tar.gz --normal-sample ${meta.patient}_${meta.normal_id}" :
"--f1r2-tar-gz ${task.ext.prefix}.f1r2.tar.gz --normal-sample ${meta.patient}_${meta.normal_id}" }
}
I overwrote this in the process scope of a separate config file provided with -c
so that is fits the sample names in my BAM files:
withName: 'MUTECT2_PAIRED' {
ext.args = { params.ignore_soft_clipped_bases ?
"--dont-use-soft-clipped-bases true --f1r2-tar-gz ${task.ext.prefix}.f1r2.tar.gz --normal-sample ${meta.normal_id}" :
"--f1r2-tar-gz ${task.ext.prefix}.f1r2.tar.gz --normal-sample ${meta.normal_id}" }
}
So you either change this config file to fit your BAM sample names or another solution would be to rename the BAM samplenames, e.g. with samtools
, so it fits the fixed naming scheme in the mutect2.config
file.
Thank you so much! changing mutect2.config worked :-)
Is this also a problem with Sarek v3.4.2?
Yes, I'm running nextflow run nf-core/sarek -r 3.4.2
Hi! YEs this is a known issue with mutect because it determines what the normal file is not by the file it is provided with but by this id
parameter. I will make a note to update the docs to more clearly explain how to run mutect2 when files are not geenrated with sarek
There is a related issue #1455. I am closing this issue and keep tracking this feature there.
Description of the bug
Hi, I run into the following error with running mutect2 via sarek:
It seems that there is something wrong with the mutect2 command in this configuration. It defines a normal sample which cannot be found by mutect2 (from the
.command.sh
):Freebayes and strelka run fine without an error message.
I have the following configuration:
Can you help me fixing this problem?
Command used and terminal output
samplesheet (example):
run command: