If you happen to see a question you know the answer to, please do chime in and help your fellow community members. We encourage our fourm members to be more involved, jump in and help out your fellow researchers with their questions. GATK forum is a community forum and helping each other with using GATK tools and research is the cornerstone of our success as a genomics research community.We appreciate your help!
Test-drive the GATK tools and Best Practices pipelines on Terra
Check out this blog post to learn how you can get started with GATK and try out the pipelines in preconfigured workspaces (with a user-friendly interface!) without having to install anything.
We will be out of the office on November 11th and 13th 2019, due to the U.S. holiday(Veteran's day) and due to a team event(Nov 13th). We will return to monitoring the GATK forum on November 12th and 14th respectively. Thank you for your patience.
HaplotypeCaller can not emit bamout in multi-threaded mode
I used multi-threading mode on HaplotypeCaller hoping to save some time. But seemed like bamout can not be emitted in multi-threading mode. I searched the answers. But I am still not sure if the latest 3.4-46 version can support multi-threading with bamout. BTW, I am still using the old 3.3-0 version. If you say yes, now 3.4 version can support multi-threading bam, then I will ask the computing core to update gatk for me. Or maybe I just delete the bamout option to save some time. But I really prefer not to do so because I need to check the depth and coverage of mapping results actually finally used for variant calling.
My command line:
java -Xmx12g -jar $GATK_JARS/GenomeAnalysisTK.jar \
-T HaplotypeCaller \
-nct 12 \
-R human_g1k_v37.fasta \
--dbsnp dbsnp_138.b37.vcf \
-I recal_realigned_b37.dedup.sorted.bam \
--genotyping_mode DISCOVERY \
-stand_emit_conf 10 \
-stand_call_conf 20 \
--emitRefConfidence GVCF \
--variant_index_type LINEAR \
--variant_index_parameter 128000 \
-o raw_var_TKDOME.g.vcf \
-bamout force_bamout_TKDOME_b37.bam -forceActive -disableOptimizations
BTW, is it necessary to add --variant_index_type LINEAR and --variant_index_parameter 128000 in Version 3.3?
Thank you very much!