Our partner Appistry (who distribute GATK and MuTect to commercial users) will be holding a webinar on 3 October. Registration is open to all; you can find more details on the Appistry website here:
Heads up, cancer researchers! Appistry (our commercial licensing partner for GATK and now MuTect) is announcing an upcoming webinar on best practices for somatic mutation studies using GATK and MuTect. Registration for the webinar is open to all (not just Appistry customers) so be sure to sign up for this. See the announcement on Appistry's website for more detailed information.
I am interested to annotate using snpEff, only those somatic mutations that were flagged as 'KEEP' in the judgement call column of the *callstats file generated from muTect. I can see that these 'KEEP' calls (in the callstats file) are flagged as 'PASS' in the 'Filter' column of the corresponding VCF file.
I am now not sure if I should filter the VCF output files from Mutect (keep only the 'PASS' calls) for snpEff annotation. snpEff does the Ti/Tv ratios apart from functional annotation, so is it expected to provide snpEff the unfiltered VCF for accurate calculation of Ti/Tv ratio OR is it Ok to provide a filtered VCF with only the passed calls?
Hello, From a talk on MuTect from a while ago, I found a reference to filtering out "noisy" reads. This seems like a great idea, and I would like to do it for other standard GATK based variant calling as well. How exactly do you do this kind of "noisy read" filtering. From the graphic in the talk, it looks like reads with a lot of mismatches relative to the others in a region, after indel realignment are candidates for being these kind of noisy reads. How is this defined exactly though, and how could I do something similar with GATK? Thanks, John