<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Liftover on Chatomics</title>
    <link>https://divingintogeneticsandgenomics.com/tags/liftover/</link>
    <description>Recent content in Liftover on Chatomics</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2018 Ming &#39;Tommy&#39; Tang</copyright>
    <lastBuildDate>Fri, 04 Apr 2014 14:44:00 -0700</lastBuildDate>
    
	<atom:link href="https://divingintogeneticsandgenomics.com/tags/liftover/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>liftover wig file</title>
      <link>https://divingintogeneticsandgenomics.com/archive/liftover-wig-file/</link>
      <pubDate>Fri, 04 Apr 2014 14:44:00 -0700</pubDate>
      
      <guid>https://divingintogeneticsandgenomics.com/archive/liftover-wig-file/</guid>
      <description>I was looking at a public ChIP-seq data set, but the author did not put the raw sequence data in the GEO database. Instead, they uploaded a wig file of the ChIP-seq signal file and it was mapped to human hg18 reference genome.
All the other data sets I am analyzing are mapped to hg19, so I have to liftover this wig file to hg19 also.
Solution: CrossMap! http://crossmap.sourceforge.net/</description>
    </item>
    
    <item>
      <title>Liftover between different Genome assemblies (hg18 to hg19)</title>
      <link>https://divingintogeneticsandgenomics.com/archive/liftover-between-different-genome-assemblies-hg18-to-hg19/</link>
      <pubDate>Sat, 20 Apr 2013 17:22:00 -0700</pubDate>
      
      <guid>https://divingintogeneticsandgenomics.com/archive/liftover-between-different-genome-assemblies-hg18-to-hg19/</guid>
      <description>see a post here:
http://manuelcorpas.com/2011/02/02/838/
Given the huge response I have at work about remapping features into another assembly, I present here an adapted version for how to remap a feature from NCBI36/hg18 to GRCh37/hg19 using UCSC’s liftOver tool.
Important: Please make sure you know in advance the assembly to which your aberration data is currently mapped to. If by mistake you remap an aberration already in GRCh37 to GRCh37 you will get new coordinates for the region mapped to the wrong coordinates.</description>
    </item>
    
  </channel>
</rss>