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.
Clarification of --normal-artifact-lod in FilterMutectCalls
The FilterMutectCalls tool doc says:
If the normal artifact log odds is larger than the threshold, then FilterMutectCalls applies the artifact-in-normal filter. For matched normal analyses with tumor contamination in the normal, consider increasing the normal-artifact-lod threshold.
This is what I understand:
The normal atrifact log odds is the threshold above which an artifactual site detected in the normal will be used to filter any variants at that site (assuming this is just a shared artifact). If there is tumor contamination of the normal, an apparent artifact in the normal may just represent tumor contamination. Hence, this threshold should be raised if we suspect tumor contamination of the normal.
Am I right?