The current GATK version is 3.7-0
Examples: Monday, today, last week, Mar 26, 3/26/04

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Did you remember to?


1. Search using the upper-right search box, e.g. using the error message.
2. Try the latest version of tools.
3. Include tool and Java versions.
4. Tell us whether you are following GATK Best Practices.
5. 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.
6. For tool errors, include the error stacktrace as well as the exact command.
7. For format issues, include the result of running ValidateSamFile for BAMs or ValidateVariants for VCFs.
8. For weird results, include an illustrative example, e.g. attach IGV screenshots according to Article#5484.
9. For a seeming variant that is uncalled, include results of following Article#1235.

Did we ask for a bug report?


Then follow instructions in Article#1894.

Formatting tip!


Surround blocks of code, error messages and BAM/VCF snippets--especially content with hashes (#)--with lines with three backticks ( ``` ) each to make a code block.
Powered by Vanilla. Made with Bootstrap.
Picard 2.9.0 is now available. Download and read release notes here.
GATK 3.7 is here! Be sure to read the Version Highlights and optionally the full Release Notes.

LiftoverVariants fails to update the header

nilshomernilshomer Boston, MAMember Posts: 13
edited May 2013 in Ask the GATK team

When running the LiftoverVariants command, the resulting VCF header has the old contig names (ex. b37 to hg19, chromosome one's name is still "1" rather than "chr1"). This only affects the header, while the variants themselves are successfully changed. I am running "2013.1-2.4.9-3-g512dc3e". The command I used is shown below:
<gatk> -R <human_g1k_v37>.fasta -T LiftoverVariants -V <in>.vcf -dict <hg19>.dict -o <out>.vcf -chain <b37tohg19>.chain

Thanks for your help!

Best Answer

  • ebanksebanks Broad InstituteMember, Broadie, Dev Posts: 692 admin
    Accepted Answer

    Hey Nils,

    LiftoverVariants is intended to be the first of 2 processing steps for the liftover; the second step is FilterLiftedVariants. In fact, LiftoverVariants is not guaranteed to produce a valid VCF file (which is alluded to in the documentation but I will go ahead and make it much more clear). If you run FilterLiftedVariants on the output of LiftoverVariants you'll see that the contig names in the header have all been correctly replaced.

    Eric Banks, PhD -- Director, Data Sciences and Data Engineering, Broad Institute of Harvard and MIT

Answers

  • ebanksebanks Broad InstituteMember, Broadie, Dev Posts: 692 admin
    Accepted Answer

    Hey Nils,

    LiftoverVariants is intended to be the first of 2 processing steps for the liftover; the second step is FilterLiftedVariants. In fact, LiftoverVariants is not guaranteed to produce a valid VCF file (which is alluded to in the documentation but I will go ahead and make it much more clear). If you run FilterLiftedVariants on the output of LiftoverVariants you'll see that the contig names in the header have all been correctly replaced.

    Eric Banks, PhD -- Director, Data Sciences and Data Engineering, Broad Institute of Harvard and MIT

Sign In or Register to comment.