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.




          "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
            Beyond CRISPR/Cas9: Understand, Choose, and Use the Right Genome Editing Tool
            by SEQadmin2



            CRISPR/Cas9 sparked the gene editing revolution for both research and therapeutics.1 But this system still showed severe issues that limited its applications. The most prominent were the heavy reliance on PAM sequences, delivery limitations, double-stranded breaks that prompt unintended edits and cell death, and editing inefficiency (both in targeting and in knock-in reliability).

            Despite this, “CRISPR helped turn genome editing from a specialized technique into
            ...
            07-31-2026, 11:01 AM
          • SEQadmin2
            Proteomic Platforms: How to Choose the Right Analytical Strategy to Improve Detection and Clinical Applications
            by SEQadmin2


            Proteomics platforms are evolving rapidly, with advances in mass spectrometry and affinity-based approaches expanding what researchers can detect and at what scale. As the field moves toward deeper proteome coverage and clinical applications, scientists face an increasingly complex landscape of tools. This article will explore how researchers are navigating these choices to find the right platform for their work.

            The systematic characterization of the human proteome has
            ...
            07-20-2026, 11:48 AM
          • 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

          ad_right_rmr

          Collapse

          News

          Collapse

          Topics Statistics Last Post
          Started by SEQadmin2, 07-31-2026, 02:55 AM
          0 responses
          18 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 07-24-2026, 12:17 PM
          0 responses
          16 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 07-23-2026, 11:41 AM
          0 responses
          16 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 07-20-2026, 11:10 AM
          0 responses
          26 views
          0 reactions
          Last Post SEQadmin2  
          Working...