-
Notifications
You must be signed in to change notification settings - Fork 594
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
Comments
That argument is only relevant to HaplotypeCaller and GenotypeGVCFs. It
should never have been available for Mutect2.
…On Thu, Mar 28, 2019, 11:09 PM igor ***@***.***> wrote:
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
<https://software.broadinstitute.org/gatk/documentation/tooldocs/4.1.0.0/org_broadinstitute_hellbender_tools_walkers_mutect_Mutect2.php>
:
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. I just wanted to confirm this was an intended change.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5845>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGRhdCF1GhJcFOFF4YvLqB_rB0x5oquxks5vbYQFgaJpZM4cRiVD>
.
|
@igordot It used to exist because
|
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 |
I just tried Mutect2 from GATK 4.1.1.0 and got an error:
From the online documentation:
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
fromFilterMutectCalls
. Are these changes explained somewhere?The text was updated successfully, but these errors were encountered: