Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • khikho
    Junior Member
    • Apr 2011
    • 2

    Velvet postprocessing problem

    when I run Postprocessor script (version 1.6 ) on my contigs (make them by velvet) I got these bunch of errors which are repeated million times , could you give me hint to handle these errors!?
    I don't know which info should I give to make the situation clear so ask me what ever makes it more clear for you!?

    Code:
    Use of uninitialized value $seq_id in print at Package/denovo_postprocessor_solid_v1.6.pl line 243, <OUT> line 272998.
    Use of uninitialized value $seq_id in split at Package/denovo_postprocessor_solid_v1.6.pl line 245, <OUT> line 272998.
    Use of uninitialized value $seq in split at Package/denovo_postprocessor_solid_v1.6.pl line 272, <OUT> line 272998.
    Use of uninitialized value $seq_id in string at Package/denovo_postprocessor_solid_v1.6.pl line 342, <OUT> line 272998.
    Use of uninitialized value $seq in concatenation (.) or string at Package/denovo_postprocessor_solid_v1.6.pl line 343, <OUT> line 272998.
    format of input wrong
    BTW I plan to assemble human genome.
    Thanks
  • colindaven
    Senior Member
    • Oct 2008
    • 417

    #2
    It's an input format error. I think this package requires an older version of Velvet.

    Why not try assembling a small subset of reads with the older Velvet version and seeing if you can get that to run ?

    Comment

    • sisch
      Member
      • Jun 2011
      • 29

      #3
      Could be an issue with the fasta headers. Could you post the first two contigs including the headers from your contigs.fa file?

      Comment

      • khikho
        Junior Member
        • Apr 2011
        • 2

        #4
        >NODE_5_length_25_cov_2.560000
        GGAAGGGCCCAAGCAACATATGGGATCGAAGAGAGCCCAGCACGGACTC
        >NODE_7_length_25_cov_2.240000
        AAACTAAACAAAACTAAACTAAACGAAACTAGACTAAACTAAACTAGAC
        >NODE_10_length_25_cov_7.920000
        GAAGGGCCACTTGGCAGCGAAGTGAAGAGTATCCAGCCGAGACGGTTCg
        >NODE_35_length_44_cov_7.863636
        TAACATAACATAAATCCAGTTAACATAACGTAACTAAAACTAATATAAACTAAACTAAGGTACACTAA

        Comment

        • sisch
          Member
          • Jun 2011
          • 29

          #5
          It seems you're trying to postprocess basespace data (as you posted) with a colorspace script (postprocessor_SOLID_v1.6.pl).

          However, I'm lacking experience with the postprocessor script, so this is the only hint I can give.

          Comment

          • jjjscuedu
            Member
            • Mar 2012
            • 35

            #6
            velveth Kmer length

            Hi all,

            I was trying to use the velveth to analysis my RNAseq dataset.

            My reads length is 101.

            However, when I try to set the Kmer of velveth to 81, there is a problem:

            velveth cannot handle the kmer as long as 81.


            Hence, i want to ask what the reasonable value for kmer for the read length.

            Thanks!

            Jingjing

            Comment

            • colindaven
              Senior Member
              • Oct 2008
              • 417

              #7
              jjjscuedu:

              Try first trimming the low quality read ends. Use FastQC to visualise.

              Then we have used successfully used kmer parameters between 33 and 45 for reads of that length. We could test values quite easily because we knew the expected genome sizes of 20 bacterial genomes, and tried to maximise for that.

              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.
                07-01-2026, 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, 07-02-2026, 11:08 AM
              0 responses
              19 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-30-2026, 05:37 AM
              0 responses
              20 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-26-2026, 11:10 AM
              0 responses
              21 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-17-2026, 06:09 AM
              0 responses
              54 views
              0 reactions
              Last Post SEQadmin2  
              Working...