Heads up:
We’re moving the GATK website, docs and forum to a new platform. Read the full story and breakdown of key changes on this blog.

gatk/haplotypecaller-gvcf-gatk4 hangs up on Firecloud

lelaginalelagina Member, Broadie


The gatk/haplotypecaller-gvcf-gatk4 workflow on Firecloud starts and hangs without producing a workflow log, JES log, stderr or stdout file.

I noticed that in runtime section for each task in wdl script for this workflow it doesn't use ${} for pass in parameters.

_runtime {
docker: docker_image
memory: mem_size
disks: "local-disk " + disk_size + " HDD"
instead of

runtime {
docker: ${docker_image}
memory: ${mem_size}
disks: "local-disk " + disk_size + " HDD"

Is this correct?

Thank you.

Best Answer


  • bshifawbshifaw Member, Broadie, Moderator admin

    The parameters should still work using that format. Were you able to successfully run the method using the test dataset and the method configuration in the featured workspace?

  • lelaginalelagina Member, Broadie

    Yes, I was able to run it. I see that in that workspace it is run on hg38 aligned bams. Is it possible to run Haplotype Caller method (haplotypecaller-gvcf-gatk4) on hg19 aligned bams? Method description doesn't specify it.

Sign In or Register to comment.