Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • yjx1217
    Member
    • Oct 2011
    • 13

    Error when running Oases for transcriptome assembly

    Hi there,

    I was using oases to do the transcriptome assembly for our RNAseq data but the computation job got terminated by an error after running for 14 hrs. It seemed that oases/velvet cannot do the assembly when kmer length equals to 33 in my case (but they worked fine for k = 21 - 31). Does anyone know the reason or has a solution? Thank you very much!

    The command I use to run oases is >>
    /home/jy16/Programs/oases-0.2.07/scripts/oases_pipeline.py -m 21 -M 35 -o pairedEnd.diginormed -d "-fastq -shortPaired asym20h.diginormed.shuffled.fastq " -p " -ins_length 300 "

    And the error message is>>

    velvetg: Could not write to pairedEnd.diginormed_33/Log: No such file or directory
    Traceback (most recent call last):
    File "/home/jy16/Programs/oases-0.2.07/scripts/oases_pipeline.py", line 121, in <module>
    main()
    File "/home/jy16/Programs/oases-0.2.07/scripts/oases_pipeline.py", line 115, in main
    singleKAssemblies(options)
    File "/home/jy16/Programs/oases-0.2.07/scripts/oases_pipeline.py", line 43, in singleKAssemblies
    assert p.returncode == 0, "Velvetg failed at k = %i\n%s" % (k, output[0])
    AssertionError: Velvetg failed at k = 33
    Last edited by yjx1217; 06-18-2012, 12:14 PM.
  • yjx1217
    Member
    • Oct 2011
    • 13

    #2
    up, any possible solution?

    Comment

    • kenietz
      Member
      • Nov 2011
      • 86

      #3
      Hi,
      i got the same error for transcriptome assembly. My command line is:

      oases_pipeline.py -m 21 -M 33 -s 4 -d "-shortPaired fw_reads.fastq_fasta" -p "-min_contig_lgth 500 -ins_length 290 -ins_length_sd 20" -o PE

      The error is:

      Traceback (most recent call last):
      File "/opt/oases/oases_pipeline.py", line 121, in <module>
      main()
      File "/opt/oases/oases_pipeline.py", line 115, in main
      singleKAssemblies(options)
      File "/opt/oases/oases_pipeline.py", line 43, in singleKAssemblies
      assert p.returncode == 0, "Velvetg failed at k = %i\n%s" % (k, output[0])
      AssertionError: Velvetg failed at k = 21


      Have no idea whats the problem though.

      Comment

      • NormSci
        Member
        • Apr 2012
        • 11

        #4
        Try posting this problem to the Oases mailing list:



        I believe it is run by DR Zerbino and MA Schultz, the creators of Oases and Velvet.
        You'll need to sign-up for an account.

        Comment

        • mestato
          Junior Member
          • Dec 2010
          • 4

          #5
          re-install velvet

          Velvet installs automatically with a max k-mer value of 31. Reinstall it with make, setting a higher max value:
          make 'MAXKMERLENGTH=70'

          Velvet manual has more info.

          Comment

          • yjx1217
            Member
            • Oct 2011
            • 13

            #6
            Thank you very much, NormSci and mestato!

            Comment

            Latest Articles

            Collapse

            • 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
            • SEQadmin2
              From Collection to Sequencing: Why Sample Preparation and Preservation Define Sequencing Data
              by SEQadmin2


              Data variability is still an issue in sequencing technologies despite the advances in reproducibility and accuracy of these platforms. But the problem does not originate in the sequencing itself, but in the previous steps, before the sample reaches the sequencer.


              The first step is collection, followed by preservation and sample preparation for analysis. Most scientists overlook those steps, but not being careful might just be skewing the experiment’s results.
              ...
              06-02-2026, 10:05 AM

            ad_right_rmr

            Collapse

            News

            Collapse

            Topics Statistics Last Post
            Started by SEQadmin2, 06-17-2026, 06:09 AM
            0 responses
            41 views
            0 reactions
            Last Post SEQadmin2  
            Started by SEQadmin2, 06-09-2026, 11:58 AM
            0 responses
            102 views
            0 reactions
            Last Post SEQadmin2  
            Started by SEQadmin2, 06-05-2026, 10:09 AM
            0 responses
            123 views
            0 reactions
            Last Post SEQadmin2  
            Started by SEQadmin2, 06-04-2026, 08:59 AM
            0 responses
            114 views
            0 reactions
            Last Post SEQadmin2  
            Working...