Description of the bug
Hello Sarek developer,
I am using Sarek pipeline (v3.0.1) to do somatic variant calling, and I started an analysis from '--step prepare_recalibration' using bam file after mark duplicates (e.g. *.md.bam); - see the command line in attached figure.
Pipeline was running normally and no errors were reported when it done, but it did not finish all steps (including variant calling) and there were no recalibrated bam files generated in output (e.g. *.recal.bam) as well. It looks the pipeline was terminated automatically after creating *.recal.table; - see attached log file.
I could not figure it out, and could you help me a troubleshooting.


Best
Sen
Command used and terminal output
No response
Relevant files
nextflow.log
System information
Nextflow version - 21.11.0
Hardware - HPC
Executor - slurm jobscript
Container engine - Singularity
OS - CentOS Linux
Version of nf-core/sarek - v3.0.1
Description of the bug
Hello Sarek developer,
I am using Sarek pipeline (v3.0.1) to do somatic variant calling, and I started an analysis from '--step prepare_recalibration' using bam file after mark duplicates (e.g. *.md.bam); - see the command line in attached figure.
Pipeline was running normally and no errors were reported when it done, but it did not finish all steps (including variant calling) and there were no recalibrated bam files generated in output (e.g. *.recal.bam) as well. It looks the pipeline was terminated automatically after creating *.recal.table; - see attached log file.
I could not figure it out, and could you help me a troubleshooting.
Best
Sen
Command used and terminal output
No response
Relevant files
nextflow.log
System information
Nextflow version - 21.11.0
Hardware - HPC
Executor - slurm jobscript
Container engine - Singularity
OS - CentOS Linux
Version of nf-core/sarek - v3.0.1