Unconfigured Ad

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

    #1

    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
        Multiomic Liquid Biopsy: What DNA/RNA Panels Reveal That DNA Alone Can’t
        by SEQadmin2



        Tumors contain complex mixtures of cell populations that evolve in response to treatment and host-specific factors. Tissue biopsies provide only static snapshots of a tumor’s state. But what if we could follow that evolution over time using a minimally invasive technique?

        Liquid biopsies can detect tumor-derived material circulating in the bloodstream, providing a way to study treatment response, detect emerging resistance, and discover new biomarkers. Circulating
        ...
        Yesterday, 09:55 AM
      • SEQadmin2
        New Genomics Technologies Take Aim at Long-Standing Limits
        by SEQadmin2


        Researchers using sequencing and genomics tools often have to make trade-offs. They can choose between speed or scale, short reads or long-range information, or targeted panels or a view of the whole transcriptome. New technologies that have been released this year are built to address those tough choices.

        We asked six companies the same four questions to learn about their latest products. The new technologies bring a lot to the table, including rethinking sequencing
        ...
        09-28-2026, 10:25 AM

      ad_right_rmr

      Collapse

      News

      Collapse

      Topics Statistics Last Post
      Started by SEQadmin2, Today, 10:52 AM
      0 responses
      8 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, Yesterday, 05:39 AM
      0 responses
      17 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 10-13-2026, 09:56 AM
      0 responses
      15 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 10-09-2026, 11:14 AM
      0 responses
      27 views
      0 reactions
      Last Post SEQadmin2  
      Working...