gatk-4.1.8.1/ValidateVariants - bypass contig length check?

September 03, 2020 15:44

Hi. I have a VCF file that was created by PLINK (derived from SNP chip data) and I seek to use GATK/ValidateVariants to confirm that the REF alleles agree with the alleged genome reference. In building the VCF, since PLINK doesn't know about any specific reference, it just puts the chromosome IDs '1','2', etc. in as the contig names (that's fine), but the contig lengths appear to be simply set from the maximum position it has for any call on that chromosome. Needless to say, that disagrees with the actual real length from the real genome, causing ValidateVariants to stop before it gets going ("Found contigs with the same name but different lengths"). Is there some way to bypass this check? possibly via "--validation-type-to-exclude"? but I don't see any option in the ValidateVariants documentation to bypass that check.

thanks.

1 comment

Genevieve Brandt

September 08, 2020 21:15
Matthew Maher here is a tutorial for ValidateSamFile that will also work for ValidateVariants. Look there for more info on how to remove those checks.
0

Comment actions Permalink

Please sign in to leave a comment.

GATK Team Out of Office

The GATK Team is out of office November 26-29 and will not be able to respond to questions. Feel free to continue to interact with other users and help each other resolve questions. If your questions are not answered, then re-post them starting November 30 with [Repost] in the title and we will get to them once we return.

GATK Showcase in Terra

Check out these fully configured workspaces to test drive the Best Practices pipelines and workshop tutorials with zero installation required!

Get email notifications!

You can opt in to receive email notifications, for example when your questions get answered or when there are new announcements on the blog, by following the instructions given here.

Got a problem?

Search using the search box at the top of the page, e.g. using the error message.
Try the latest version of tools.
When reporting a problem, include tool and Java versions.
Tell us whether you are following GATK Best Practices.
Include relevant details, e.g. platform, DNA- or RNA-Seq, WES (+capture kit) or WGS (PCR-free or PCR+), paired- or single-end, read length, expected average coverage, somatic data, etc.
For tool errors, include the error stacktrace as well as the exact command.
For format issues, include the result of running ValidateSamFile for BAMs or ValidateVariants for VCFs.
For weird results, include an illustrative example, e.g. attach IGV screenshots.

Did we ask for a bug report?

Then follow these instructions.

Did we give you a GitHub issue to track?

If you're not familiar with Github here are some basics to help.

Genome Analysis Toolkit

Need Help?

Community Forum