HgLiftOver: Difference between revisions

From genomewiki
Jump to navigationJump to search
mNo edit summary
 
No edit summary
Line 1: Line 1:
[http://genome.ucsc.edu/cgi-bin/hgLiftOver HgLiftOver] is a Genome Browser utility for converting genome coordinates between assemblies.
[http://genome.ucsc.edu/cgi-bin/hgLiftOver HgLiftOver] is a Genome Browser utility for converting genome coordinates between assemblies.


This page could be expanded to include all kinds of information about hgLiftOver.
This page could be expanded to include all kinds of information about hgLiftOver.  For now it just has a section on a point of confusion about hgLiftOver and BED format.


== hgLiftOver and BED format ==
== hgLiftOver - BED vs. Position format ==
Sometimes when one converts coordinates using hgLiftOver using position format and then tries it again using BED format, it looks like the BED format results are incorrect.  This happens when (1) the input used for BED is the exact same as that used for position (i.e., the first coordinate is not lowered by one to turn it into BED format) and (2) the converted section in the new assembly is on a strand with the  opposite orientation of the original section (i.e., the net and chain tracks appear to be on the negative strand).


Here is an example of this potentially confusing case -- conversion of the rn4 gene Apo-E to hg18 coordinates.


First, the '''hgConvert''' results from rn4 to hg18:
  Rat Nov. 2004 chr1:79003641-79006387 to Human Mar. 2006
  chr19:50100923-50104476 (73.9% of bases, 100.0% of span)


rn4 default to hg18
And the exact same results from hgLiftOver, using the POS option:
 
  chr1:79003641-79006387 (rn4)
hgConvert:
  chr19:50100923-50104476 (hg18) <-- same as hgConvert.
Rat Nov. 2004 chr1:79003435-79006520 to Human Mar. 2006
chr19:50100786-50104563 (72.7% of bases, 96.3% of span)
 
POS:
chr1:79003435-79006520 (rn4)
chr19:50100786-50104563 (hg18) <-- same as hgConvert.
BED (same numbers as POS):
Now, if we try to convert the exact same coordinates, but take out the position punctuation so that it looks like BED format (this is the incorrect way to do it):
chr1 79003435 79006520 x (rn4)
  chr1 79003641 79006387 x (rn4)
chr19 50100785 50104563 x 1 (hg18) <-- start is two low.
  chr19 50100922 50104475 x 1 (hg18) <-- in Browser position coordinates, this is chr19:50100923-50104475.
 
This is NOT the same result as we got with position.
BED (converted to correct):
chr19 50100784 50104563 x (rn4)
chr16 83161495 83167176 x 1 (hg18) <-- when converted back to browser coords, it's the same as position/hgConvert (chr19:50100786-50104563)
 


Here is a BED conversion using the correct coordinates for BED format:
  chr1 79003640 79006387 x (rn4)
  chr19 50100922 50104476 x 1 (hg18) <-- in Browser position coordinates, this is chr19:50100923-50104476.
The same result as the position method!




[[Category:Technical FAQ]]
[[Category:Technical FAQ]]

Revision as of 01:59, 23 December 2006

HgLiftOver is a Genome Browser utility for converting genome coordinates between assemblies.

This page could be expanded to include all kinds of information about hgLiftOver. For now it just has a section on a point of confusion about hgLiftOver and BED format.

hgLiftOver - BED vs. Position format

Sometimes when one converts coordinates using hgLiftOver using position format and then tries it again using BED format, it looks like the BED format results are incorrect. This happens when (1) the input used for BED is the exact same as that used for position (i.e., the first coordinate is not lowered by one to turn it into BED format) and (2) the converted section in the new assembly is on a strand with the opposite orientation of the original section (i.e., the net and chain tracks appear to be on the negative strand).

Here is an example of this potentially confusing case -- conversion of the rn4 gene Apo-E to hg18 coordinates.

First, the hgConvert results from rn4 to hg18:

 Rat Nov. 2004 chr1:79003641-79006387 to Human Mar. 2006
 chr19:50100923-50104476 (73.9% of bases, 100.0% of span)

And the exact same results from hgLiftOver, using the POS option:

 chr1:79003641-79006387 (rn4)
 chr19:50100923-50104476 (hg18) <-- same as hgConvert.

Now, if we try to convert the exact same coordinates, but take out the position punctuation so that it looks like BED format (this is the incorrect way to do it):

 chr1 79003641 79006387 x (rn4)
 chr19 50100922 50104475 x 1 (hg18) <-- in Browser position coordinates, this is chr19:50100923-50104475.

This is NOT the same result as we got with position.

Here is a BED conversion using the correct coordinates for BED format:

 chr1 79003640 79006387 x (rn4)
 chr19 50100922 50104476 x 1 (hg18) <-- in Browser position coordinates, this is chr19:50100923-50104476.

The same result as the position method!