Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • bair
    Member
    • Jan 2010
    • 65

    compare structural variation

    Dear all,

    How to compare structural variation in two genomes or with database like DGV?

    Software like breakdancer can do structural variation analysis, it outputs INV, DEL, INS and other types of SV, how can I compare it with DGV?

    Simply to see if any of the two chromosome coordinates in breakdancer file locate in DGV locus region?


    Many thanks!
  • Irsan_Kooi
    Member
    • Mar 2011
    • 10

    #2
    Hi Bair,

    I am having the same problem. Using breakdancer the output consists of DEL, INV, INS, CTX and ITX. Though breakdancer tries to support detection of somatic variants I don't think it is working very well... In the 11th output column it displays the amount of reads supporting the called SV per bam-file. So if you have run:

    [your_prompt]$ bam2cfg.pl -g -h tumor.bam normal.bam > config_file.cfg
    [your_prompt]$ breakdancer_max -d some_prefix config.txt > tumor_normal.ctx

    then the 11the column displays the amount of reads supporting the called SV. But at first, it does not work if you don't have set the read-group information correctly (as is said in the breakdancer documentation). But more importantly, if you filter your results for SVs were this 11th column says that the SV is only supported by reads of your tumor.bam file it does not look very somatic if you view the results in IGV. Not for deletions (which I think are easiest to compare), not even talking about the others.

    I think the best way to go is to run breakdancer on the two .bam files seperately and then use secondary tools to compare the results.

    For Deletions, you can make 2 bed files for all locations that are deleted in your 2 bam files. Than you can use intersectBed from BEDtools to find the deletions in your tumor results that are not present in your control results:

    [your_prompt]intersectBed -v -f 0.5 -a tumor_breakdancer_deletions.bed -b control_breakdancer_deletions.bed

    For inversions, insertions, inter- and intra chromosomal SVs the situation looks slightly different to me. Here the breakpoints are of imporantence, not the location from start to end (like when looking at deletions). I think you should make a list of all breakpoints, use a buffer size (say +- 500 bps) and see which breakpoints are present in your tumor and not in your control (maybe the same way using bedtools?)

    So far, I have successfully compared breakdancer deletions between samples but am just starting to implement a comparison tool for the other types of SVs

    Please feel free to share some thoughts about this.

    Cheers,

    Irsan

    Comment

    Latest Articles

    Collapse

    • SEQadmin2
      Advanced Sequencing Platforms Tackle Neuroscience’s Toughest Genomics Problems
      by SEQadmin2



      Genomics studies in neuroscience face a special challenge due to the brain’s complexity and scarcity of samples. Mapping changes in cell type and state using conventional next-generation sequencing methods remains challenging. Advances in technologies like single-cell sequencing, spatial transcriptomics, and long-read sequencing have opened the door to deeper studies of the brain and diseases like Alzheimer’s, amyotrophic lateral sclerosis (ALS), and schizophrenia.
      ...
      07-09-2026, 11:10 AM
    • 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...
      07-08-2026, 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

    ad_right_rmr

    Collapse

    News

    Collapse

    Topics Statistics Last Post
    Started by SEQadmin2, 07-13-2026, 10:26 AM
    0 responses
    22 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 07-09-2026, 10:04 AM
    0 responses
    32 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 07-08-2026, 10:08 AM
    0 responses
    20 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 07-07-2026, 11:05 AM
    0 responses
    34 views
    0 reactions
    Last Post SEQadmin2  
    Working...