You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running haplotypecaller without a dbsnps or known-sites parameter (e.g., with non-human organisms) two unusual behaviors occur with the output:
If not ran with --skip_step haplotypecaller_filter, the haplotypecaller vcf files are not carried downstream into any further steps like multiqc.
If ran with --skip_step haplotypecaller_filter the outputs are carried into multiqc, but are not ran with add_info_to_vcf.
The problem appears to be in the VCF_VARIANT_FILTERING_GATK subworkflow and drops the haplotypecaller output after attempting to call FILTERVARIANTTRANCHES
Description of the bug
When running haplotypecaller without a dbsnps or known-sites parameter (e.g., with non-human organisms) two unusual behaviors occur with the output:
The problem appears to be in the VCF_VARIANT_FILTERING_GATK subworkflow and drops the haplotypecaller output after attempting to call FILTERVARIANTTRANCHES
Command used and terminal output
Relevant files
No response
System information
nextflow v23.10.0.5889
Cloud (32cpu, 512Gb RAM)
Executor (local)
Container: Docker
OS: Ubuntu
Sarek: 3.3.2
The text was updated successfully, but these errors were encountered: