If you happen to see a question you know the answer to, please do chime in and help your fellow community members. We encourage our fourm members to be more involved, jump in and help out your fellow researchers with their questions. GATK forum is a community forum and helping each other with using GATK tools and research is the cornerstone of our success as a genomics research community.We appreciate your help!
Test-drive the GATK tools and Best Practices pipelines on Terra
Check out this blog post to learn how you can get started with GATK and try out the pipelines in preconfigured workspaces (with a user-friendly interface!) without having to install anything.
The SVVariantAnnotator walker is a general framework for making different
annotations on VCF files containing structural variant records.
SVVariantAnnotator is conceptually similar to the GATK VariantAnnotator
walker, but is tailed for use with structural variations. Each annotator is
like a plug-in and you can run one or more annotators over the same file in
Each annotator can either add annotations (typically INFO fields) to the input
VCF file, or it can generate a textual report (e.g. tab delimited) for
additional processing, or it can generate one or more summary reports (also
text files) or all of the above. Different annotators may or may not support
all modes of operation.
The following annotators are currently implemented:
3. Common Arguments
The following common arguments are handled by the SVVariantAnnotator walker
-A <annotation>: The name of the annotation(s) you want to run.
-B:variant,VCF ''input-vcf-file'': The input VCF file is
supplied to SVVariantAnnotator as a ROD binding using the generic GATK
argument. : The input VCF file must be sorted in coordinate order based on the
-BTI variant: You should always pass this generic GATK flag when running
SVVariantAnnotator to drive iteration over the input VCF file. Note that
-R '<reference-sequence>: Indexed fasta file containing the reference
-writeReport: Flag indicating that the annotator should print a report file
(default false). : Typically, this will contain one line per VCF record and
will contain the same information as the annotations that would be stored in
the VCF file, but may be easier to parse.
-writeSummary: Flag indicating that the annotator should write a summary
file (default false). : Depending on the annotator, the summary file produces
information organized in different ways. : For example, the VariantsPerSample
annotator produces a summary file containing a row for each sample and the
count of variants in that sample.
-reportDirectory <directory>: The directory to write report files and
summary files (default is the current directory).
-tempDir <directory>: The directory to use store temporary files.
-O <output-file>: The destination for the output VCF file. : If you do
-O, then the annotator will not produce VCF annotations (but may
produce reports or summaries).
-reportFile <file-path>: The path and file name for the report file. This
overrides -reportDirectory. : If not supplied, the report file is based on the
name of the annotator (and will be in the report directory).
-summaryFile <file-path>: The path and file name for the summary file.
-reportDirectory: If not supplied, each annotator generates a
default summary file name (if the annotator supports writing summary files).
Available in SVToolkit version 1.04.