Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mutect2 standard-min-confidence-threshold-for-calling #5845

Closed
igordot opened this issue Mar 29, 2019 · 3 comments
Closed

Mutect2 standard-min-confidence-threshold-for-calling #5845

igordot opened this issue Mar 29, 2019 · 3 comments
Assignees
Labels

Comments

@igordot
Copy link

igordot commented Mar 29, 2019

I just tried Mutect2 from GATK 4.1.1.0 and got an error:

A USER ERROR has occurred: standard-min-confidence-threshold-for-calling is not a recognized option

From the online documentation:

Note that the default was changed from 10.0 to 30.0 in version 4.1.0.0 to accompany the switch to use the the new quality score by default.

Thus, it was still maintained in 4.1.0.0. Based on that, I am surprised that it was removed.

There are actually a few other parameters that got dropped. For example, normal-artifact-lod from FilterMutectCalls. Are these changes explained somewhere?

@ldgauthier
Copy link
Contributor

ldgauthier commented Mar 29, 2019 via email

@davidbenjamin
Copy link
Contributor

@igordot It used to exist because AssemblyBasedCallerArgumentCollection used to extend StandardCallerArgumentCollection, causing Mutect2 to have a bunch of HaplotypeCaller arguments that it didn't use. This was fixed in PR #5758.

FilterMutectCalls also lost a few arguments as part of a huge change to the entire filtering model in PR #5688. I'm working on a blog post about this but for now the Mutect2 docs at https://github.com/broadinstitute/gatk/blob/master/docs/mutect/mutect.pdf are up-to-date and more user-friendly than they used to be.

@davidbenjamin
Copy link
Contributor

If you get any more of these errors, it's either an argument that never had any effect or something that you 4.1.1 got rid of. In the latter case, you don't need to replace it with anything. In 4.1.1 FilterMutectCalls automatically learns a lot of parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants