Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Slacanch
    Member
    • Jan 2013
    • 10

    SGD liftOver chain files issue

    SGD (Saccharomyces Genome Database), contains a repository of liftOver chain files that allow to convert form any version of the reference genome to the last one.

    after trying, and failing multiple times, to convert between two assemblies, i decided to take a look at the chain files themselves and i compared the chain files provided from sgd with the same file provided by the ucsc genome browser (R61 to R64 from sgd, sacCer2 to sacCer3 from ucsc).

    the result is rather odd; this is the beginning of the file in the two instances:

    UCSC:

    Code:
    chain 21724089 chrI 230208 + 0 230208 chrI 230218 + 0 230218 16
    3834	1	0
    2091	0	1
    527	1	0
    10002	1	1
    10	1	0
    29	1	0
    SGD:

    Code:
    chain 21724089 chr01_2008_03_05 230208 + 0 230208 chr01_2011_02_03 230218 + 0 230218 1
    3834	1	0
    2091	0	1
    527	1	0
    10002	1	1
    10	1	0
    29	1	0

    most of the file is actually the same, but the definition of the chromosomes is really strange, it has dates attached! which render the file practically useless (i've managed to successfully liftover using the ucsc chain file, while i could not using th SGD one)

    Code:
    chrI 230208   vs     chr01_2008_03_05 230208
    the strange pattern repeats for every chromosome in the sgd file.



    is there something i missed? am i the only one having this issue? what is the meaning of this thing? i am confused
  • raim
    Junior Member
    • Jun 2016
    • 2

    #2
    sgd liftover problem solved?

    Hi Slacanch,
    Have you ever managed to solve this problem?
    best,
    Rainer

    Comment

    • raim
      Junior Member
      • Jun 2016
      • 2

      #3
      Hi,

      The SGD helpdesk said the date appendix in chromosome names can just be deleted.
      Also, at least the liftOver reimplementation in R/bioconductor's rtracklayer can't handle the comment lines starting with ##.

      So the following command-line processing seems to do the trick, although I have not tested the actual mapping result yet:

      grep -v "##" V43_2004_07_26_V64_2011_02_03.over.chain | sed 's/\(chr..\)_[^ ]*/\1/g' > V43_2004_07_26_V64_2011_02_03_fixed.over.chain

      Note that in your case you would still need to convert the roman chromosome numbers
      to two digit arabic, e.g. chrI should be chr01. And watch mitochondrial chromosomes, chrM is not chr1000

      Rainer
      Last edited by raim; 02-28-2018, 11:50 PM.

      Comment

      Latest Articles

      Collapse

      • SEQadmin2
        Cancer Drug Resistance: The Lingering Barrier to Rising Survival
        by SEQadmin2



        Cancer survival rates have significantly increased in the last few decades in the United States, reaching a combined 70% 5-year survival rate by 2021. Behind this number, there are years of research to find new therapies, drug targets, and early detection methods. But there is one core challenge that keeps slowing down these advances, and it’s about drug resistance.

        There is no single reason why many patients don’t respond to treatment as expected. Cancer is...
        Today, 05:17 AM
      • GATTACAT
        Reply to Nine Things a Sample Prep Scientist Thinks About Before Sequencing
        by GATTACAT
        Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.
        07-01-2026, 11:43 AM
      • SEQadmin2
        Nine Things a Sample Prep Scientist Thinks About Before Sequencing
        by SEQadmin2


        I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.

        Here are nine questions we think about, in roughly the order they matter, before...
        06-18-2026, 07:11 AM

      ad_right_rmr

      Collapse

      News

      Collapse

      Topics Statistics Last Post
      Started by SEQadmin2, Today, 10:08 AM
      0 responses
      6 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, Yesterday, 11:05 AM
      0 responses
      7 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 07-02-2026, 11:08 AM
      0 responses
      31 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-30-2026, 05:37 AM
      0 responses
      28 views
      0 reactions
      Last Post SEQadmin2  
      Working...