Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • akshaya.ramesh
    Member
    • Apr 2013
    • 22

    #1

    issue running Velvet optimizer

    Hello,
    I have been using Velvet to perform a denovo assembly and recently came across the Velvet Optimizer program that would help optimizing the input parameters for Velvet to perform a good assembly. I seem to be running into the same error while running Velvet Optimizer for the past few days.

    I use the following command line to run the perl script:

    VelvetOptimiser.pl -s 21 -e 91 -m 0.001 -o -exp_cov 0.000001 -f -bam /windows/D/genomes/macaca/paired_merged_Ig_TCR.bam -d /windows/D/genomes/macaca/Velvet_optimized

    and the following error shows up:

    Minimum specified coverage cutoff is higher than the expected coverage. Please choose a minimum coverage cutoff smaller than 0 and re-run.

    I have tried several modifications (change m, the expected coverage, change the default values in the actual script) and different data sets, but I have not been able to proceed further/get rid of the error.

    My background in linux/computer science is a month old, so my question might seem very basic and I apologize in advance. Any help would be appreciated Thanks in advance for your time!
  • mastal
    Senior Member
    • Mar 2009
    • 666

    #2
    issue running Velvet optimizer

    Hi,

    -m specifies the minimum coverage cutoff, the default value is 0.

    As the error message says, you have chosen a coverage cutoff (-m 0.001), which is higher than the expected coverage (-exp_cov 0.000001).

    When you run velvetg, if you select -exp_cov auto, -cov_cutoff auto, velvet sets the -cov_cutoff to half the value of -exp_cov.

    What are you trying to assemble, and why are you using such a low value for -exp_cov?

    best wishes,
    maria

    Comment

    • akshaya.ramesh
      Member
      • Apr 2013
      • 22

      #3
      Hello,

      Thank you so much for getting back to me.

      I understand that -m specifies the minimum coverage cutoff. I am trying to optimize and determine the best parameters that would help me perform denovo assembly of the macaque genome where the expected coverage cutoff is 50. However, when I actually run Velvet the coverage of the contigs generated are not anywhere near 50. Also, when I try running Velvet optimizer with no specification of -exp_cov; I still get the same error message.

      These are the commands that I use:
      VelvetOptimiser.pl -s 21 -e 91 -m 0.001 -o -exp_cov auto -f -bam /windows/D/genomes/macaca/paired_merged_Ig_TCR.bam -d /windows/D/genomes/macaca/Velvet_optimized

      VelvetOptimiser.pl -s 21 -e 91 -m 0.001 -f -bam /windows/D/genomes/macaca/paired_merged_Ig_TCR.bam -d /windows/D/genomes/macaca/Velvet_optimized

      Initially I did not specify a minimum coverage cutoff/expected coverage. I reduced the mim covergae cutoff to 0.001 just to see if that would get rid of the error message. It was silly of me to reduce the exp coverage below the min coverage cutoff though. I am not sure about what I should change/specify when I run the optimizer to get it to analyze the data.

      Comment

      • mastal
        Senior Member
        • Mar 2009
        • 666

        #4
        issue running Velvet optimizer

        I would try running VelvetOptimiser with your calculated value of -exp_cov, and leave -m at the default value of 0.

        see the formula in the velvet manual for calculating expected coverage using the kmer lengths.

        Comment

        • akshaya.ramesh
          Member
          • Apr 2013
          • 22

          #5
          Thank you for the help. I wrote to Dr. Torsten Seemann and he told me that I was running into issues because my -m and -o options were not in quotes as well. I changed the exp coverage, and now that my -m and -o options are in quotes the script is now running!

          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

          ad_right_rmr

          Collapse

          News

          Collapse

          Topics Statistics Last Post
          Started by SEQadmin2, Today, 12:22 PM
          0 responses
          12 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 08-11-2026, 10:35 AM
          0 responses
          11 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 08-06-2026, 07:41 AM
          0 responses
          30 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 08-03-2026, 10:13 AM
          0 responses
          48 views
          0 reactions
          Last Post SEQadmin2  
          Working...