Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • hard998
    Junior Member
    • Jun 2009
    • 4

    contig overlaps in velvet 1.2.03

    Hi, I did a denovo assembly using velvet 1.2.03 which gave me 1626 contigs,

    However, when I examined the contig.fa output by velvet, eg
    >NODE_1331_length_2655_cov_63.920151
    >NODE_1395_length_1978_cov_42.813953
    ...

    I found 689 contigs have tail-to-tail matches with each other by doing BLAST, such as
    NODE_1331_length_2655_cov_63.920151: 2656 tgcggctggtcggctcgtcgcaggcgaacatgttcgcctccatc 2699
    ||||||||||||||||||||||||||||||||||||||||||||
    NODE_1395_length_1978_cov_42.813953: 2022 tgcggctggtcggctcgtcgcaggcgaacatgttcgcctccatc 1979


    Can anyone tell me why didn't velvet merge those overlaps? Is that correct for me to join contigs into larger contigs? Thank you!
  • seb567
    Senior Member
    • Jul 2008
    • 260

    #2
    Originally posted by hard998 View Post
    Hi, I did a denovo assembly using velvet 1.2.03 which gave me 1626 contigs,

    However, when I examined the contig.fa output by velvet, eg
    >NODE_1331_length_2655_cov_63.920151
    >NODE_1395_length_1978_cov_42.813953
    ...

    I found 689 contigs have tail-to-tail matches with each other by doing BLAST, such as
    NODE_1331_length_2655_cov_63.920151: 2656 tgcggctggtcggctcgtcgcaggcgaacatgttcgcctccatc 2699
    ||||||||||||||||||||||||||||||||||||||||||||
    NODE_1395_length_1978_cov_42.813953: 2022 tgcggctggtcggctcgtcgcaggcgaacatgttcgcctccatc 1979


    Can anyone tell me why didn't velvet merge those overlaps? Is that correct for me to join contigs into larger contigs? Thank you!
    These are called repeats. You probably have more than 2 contigs with this sequence on one end. Therefore, Velvet did not merge them because that would cause an assembly error, which produce chimeric contigs.

    Comment

    Latest Articles

    Collapse

    • 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, 07-02-2026, 11:08 AM
    0 responses
    25 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 06-30-2026, 05:37 AM
    0 responses
    23 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 06-26-2026, 11:10 AM
    0 responses
    23 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 06-17-2026, 06:09 AM
    0 responses
    55 views
    0 reactions
    Last Post SEQadmin2  
    Working...