Showing docs for version 3.6-0 | The latest version is 4.1.4.0


HaplotypeResolver

Haplotype-based resolution of variants in separate callsets.

Category Variant Manipulation Tools

Traversal LocusWalker

PartitionBy LOCUS


Overview

HaplotypeResolver is a tool that takes two VCF files and constructs haplotypes based on the variants inside them. From that, it can resolve potential differences in variant calls that are inherently the same (or similar) variants. Records are annotated with the set and status attributes.

Input

Two variant files to resolve.

Output

A single consensus VCF.

Usage example

 java -jar GenomeAnalysisTK.jar \
   -T HaplotypeResolver \
   -R reference.fasta \
   -V:v1 input1.vcf \
   -V:v2 input2.vcf \
   -o output.vcf
 

Additional Information

Read filters

These Read Filters are automatically applied to the data by the Engine before processing by HaplotypeResolver.

Window size

This tool uses a sliding window on the reference.

  • Window start: -1,100 bp before the locus
  • Window stop: 1,100 bp after the locus

Command-line Arguments

Engine arguments

All tools inherit arguments from the GATK Engine' "CommandLineGATK" argument collection, which can be used to modify various aspects of the tool's function. For example, the -L argument directs the GATK engine to restrict processing to specific genomic intervals; or the -rf argument allows you to apply certain read filters to exclude some of the data from the analysis.

HaplotypeResolver specific arguments

This table summarizes the command-line arguments that are specific to this tool. For more details on each argument, see the list further down below the table or click on an argument name to jump directly to that entry in the list.

Argument name(s) Default value Summary
Required Inputs
--variant
 -V
NA Input VCF file
Optional Outputs
--out
 -o
stdout File to which variants should be written
Optional Parameters
--setKey
set Key used in the INFO key=value tag emitted describing which set the combined VCF record came from
--statusKey
status Key used in the INFO key=value tag emitted describing the extent to which records match

Argument details

Arguments in this list are specific to this tool. Keep in mind that other arguments are available that are shared with other tools (e.g. command-line GATK arguments); see Inherited arguments above.


--out / -o

File to which variants should be written

VariantContextWriter  stdout


--setKey / -setKey

Key used in the INFO key=value tag emitted describing which set the combined VCF record came from
Set to 'null' if you don't want the set field emitted.

String  set


--statusKey / -statusKey

Key used in the INFO key=value tag emitted describing the extent to which records match
Set to 'null' if you don't want the status field emitted.

String  status


--variant / -V

Input VCF file

This argument supports reference-ordered data (ROD) files in the following formats: BCF2, VCF, VCF3

R List[RodBinding[VariantContext]]  NA


Return to top


See also GATK Documentation Index | Tool Docs Index | Support Forum

GATK version 3.6-0-g89b7209 built at 2017/02/09 12:52:48.