Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • plumb
    Member
    • Sep 2009
    • 15

    meta-velvetg cannot detect peak errors

    I am running my illumina data using metavelvet. I got the following message. Anybody has experiences with that?

    Thank you in advance.

    Writing into graph file k51/Graph...
    WARNING: NO COVERAGE CUTOFF PROVIDED
    Velvet will probably leave behind many detectable errors
    See manual for instructions on how to set the coverage cutoff parameter
    Writing into stats file k51/stats_EstimateCovMulti.txt...
    Starting peak detection...
    Error!! Couldn't detect any peaks
  • seb567
    Senior Member
    • Jul 2008
    • 260

    #2
    Originally posted by plumb View Post
    I am running my illumina data using metavelvet. I got the following message. Anybody has experiences with that?

    Thank you in advance.

    Writing into graph file k51/Graph...
    WARNING: NO COVERAGE CUTOFF PROVIDED
    Velvet will probably leave behind many detectable errors
    See manual for instructions on how to set the coverage cutoff parameter
    Writing into stats file k51/stats_EstimateCovMulti.txt...
    Starting peak detection...
    Error!! Couldn't detect any peaks
    First, you can try with a lower value for the k-mer length.

    51 is very high -- Velvet does not correct your reads for errors. Therefore, most of your k-mers will likely have a depth of 1 or 2.

    I suggest you try 21 as a test.


    Also, you won't have any peak in most real metagenomes.




    We use Ray to assemble gut microbiomes and it works well.


    How to use Ray:

    HTML Code:
    mpiexec -n 64 Ray \
     -k \
     31 \
     -p \
     Sample/ERR011142_1.fastq.gz \
     Sample/ERR011142_2.fastq.gz \
     -p \
     Sample/ERR011143_1.fastq.gz \
     Sample/ERR011143_2.fastq.gz \
     -o \
     Assembly

    Sébastien Boisvert

    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.
      Yesterday, 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, Today, 11:08 AM
    0 responses
    6 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 06-30-2026, 05:37 AM
    0 responses
    11 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 06-26-2026, 11:10 AM
    0 responses
    18 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 06-17-2026, 06:09 AM
    0 responses
    52 views
    0 reactions
    Last Post SEQadmin2  
    Working...