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.
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 for a Broad Institute event from Dec 10th to Dec 11th 2019. We will be back to monitor the GATK forum on Dec 12th 2019. In the meantime we encourage you to help out other community members with their queries.
Thank you for your patience!
Somatic mutation pipeline error at"WorkflowManagerActor Workflow 709e5b32-05c0-4e49-96b7-bc5c4ab56"
Dear GATK team,
I am trying to call somatic mutation by using best practice pipeline for somatic mutation calling. Almost all data was successfully called somatic mutation in VCF files. However, several files were failed to run on the way of pipeline. Here, I picked up to the error strings from logs. Do you have any suggestions why this problem was occurred?
1. gatk docker: broadinstitute/gatk 188.8.131.52, 123712a62f94
2. GATK: v184.108.40.206
3. openjdk version "1.8.0_191"
4. OpenJDK Runtime Environment (build 1.8.0_191-8u191-b12-2ubuntu0.16.04.1-b12)
5. OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode
in output log
[2019-02-08 00:55:32,66] [error] WorkflowManagerActor Workflow 709e5b32-05c0-4e49-96b7-bc5c4ab56256 failed (during ExecutingWorkflowState): Job Mutect2.M2:4:1 exited with return code 1 which has not been declared as a valid return code. See 'continueOnReturnCode' runtime attribute for more details. Check the content of stderr for potential additional information: /transient/suimye/181016LUAD/180207_singlerun/cromwell-executions/Mutect2/709e5b32-05c0-4e49-96b7-bc5c4ab56256/call-M2/shard-4/execution/stderr. Picked up _JAVA_OPTIONS: -Djava.io.tmpdir=/cromwell-executions/Mutect2/709e5b32-05c0-4e49-96b7-bc5c4ab56256/call-M2/shard-4/tmp.5a9c12c6
(There is no error information in /call-M2/shared-4/execution/stderr. The pipeline was stopped in the step "shard-4". I copied the last strings in the stderr file.)