Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ytmnd85
    Member
    • Apr 2009
    • 10

    #1

    Velvet - stats output - min_contig_length

    I am attempting to use Velvet to analyze some data from our lab. During a practice run, I noticed that the output from velvet had some odd contigs (length 1, coverage 300,000), so I decided to place some parameters on it. I set the minimum coverage to 10, and the minimum contig length to 10. When I checked the new output, the minimum coverage had been implemented, but it didn't appear that the minimum contig length had. Looking at the stats file, I still had contigs of length 1. However, upon looking at the contigs.fa file, I found that my contig length had been implemented.

    Does anyone know why my contig file is correct, but my stats file does not reflect my contig-length restriction?
  • Zigster
    Jeremy Leipzig
    • May 2009
    • 117

    #2
    Does anyone know why my contig file is correct, but my stats file does not reflect my contig-length restriction?
    yeah that parameter only affects the contigs.fa file (as you have already discovered)

    min_contig_length is just a dumb cutoff included for convenience - a two-line perl script could accomplish the same thing

    cov_cutoff is a real parameter that can actually change the assembly in unexpected ways

    and also note that length in the stats.txt file is in kmers, not bp
    --
    Jeremy Leipzig
    Bioinformatics Programmer
    --
    My blog
    Twitter

    Comment

    • ytmnd85
      Member
      • Apr 2009
      • 10

      #3
      Thank you,
      That makes sense now. It just had me perplexed when I was trying to interpret my results and I was seeing contradicting files.

      Comment

      • mmmm
        Senior Member
        • Jul 2013
        • 131

        #4
        kmer to nucleotide

        Originally posted by Zigster View Post
        yeah that parameter only affects the contigs.fa file (as you have already discovered)

        min_contig_length is just a dumb cutoff included for convenience - a two-line perl script could accomplish the same thing

        cov_cutoff is a real parameter that can actually change the assembly in unexpected ways

        and also note that length in the stats.txt file is in kmers, not bp
        in stats.txt (velvet output) how to convert node length to the actual nucleotide length, for example, if the node length is 1what would be the nucleotide length?

        Comment

        • mastal
          Senior Member
          • Mar 2009
          • 666

          #5
          see the equation for calculating kmer coverage from nucleotide coverage in the velvet manual.

          http://www.ebi.ac.uk/~zerbino/velvet/


          "The relation between k-mer coverage Ck and standard (nucleotide-wise) coverage C is Ck = C (L−k +1)/L where
          k is your hash length, and L you read length."


          Node length = Contig length in nucleotides minus k-mer length + 1.
          Last edited by mastal; 01-24-2014, 05:53 AM.

          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
            ...
            10-14-2026, 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, 10-22-2026, 11:13 AM
          0 responses
          42 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 10-22-2026, 10:48 AM
          0 responses
          33 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 10-15-2026, 10:52 AM
          0 responses
          44 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 10-14-2026, 05:39 AM
          0 responses
          45 views
          0 reactions
          Last Post SEQadmin2  
          Working...