Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • zjrouc
    Member
    • Sep 2010
    • 25

    abyss error

    Hi,
    I am doing an ABySS assembly recently. Here is the problem i met:

    Mapped 419743499 of 454426594 reads (92.4%)
    Mapped 419741912 of 454426594 reads uniquely (92.4%)
    Read 454426594 alignments
    Mateless 454426594 100%
    Unaligned 0
    Singleton 0
    FR 0
    RF 0
    FF 0
    Different 0
    Total 454426594
    error: the histogram `scale-3.hist' is empty
    sort: write failed: standard output: Broken pipe
    sort: write error
    make: *** [scale-3.dist] Error 1
    make: *** Deleting file `scale-3.dist'

    Could anyone help me figure this out?
  • Wallysb01
    Senior Member
    • Feb 2011
    • 286

    #2
    That seems very odd. What was the command line that got you this far and the rest of the output?

    Also, the ABySS user group is usually pretty helpful. So you might try there too.

    Comment

    • zjrouc
      Member
      • Sep 2010
      • 25

      #3
      Hi,
      Here is the script i used.

      for k in {56..60}; do mkdir k$k; cd k$k; abyss-pe k=$k name=scale in='/scratch/zjr/scale/data/trimedpaired.fasta' OVERLAP_OPTIONS=--no-scaffold SIMPLEGRAPH_OPTIONS=--no-scaffold E=1 n=10 v=-v; cd ..; done

      Comment

      • zjrouc
        Member
        • Sep 2010
        • 25

        #4
        By the way, the other output seems fine. No error report else was found.

        Comment

        • Wallysb01
          Senior Member
          • Feb 2011
          • 286

          #5
          Do your reads have /1 and /2 after them? Otherwise, I don't think ABySS can understand the paired information.

          Comment

          • zjrouc
            Member
            • Sep 2010
            • 25

            #6
            For example, the first two paired reads in fasta file were displayed with head:
            >HWI-ST1280:130:C1GYVACXX:8:1101:1161:2106_1:N:0:GGCTAGA
            >HWI-ST1280:130:C1GYVACXX:8:1101:1161:2106_2:N:0:GGCTAGA
            which were transformed from fastq file.

            Is this the problem?

            Comment

            • Wallysb01
              Senior Member
              • Feb 2011
              • 286

              #7
              I think so. From the documentation, either the names have to be the same, which they aren't, or you need a /1 and /2 to end them.

              You could use sed to fix them something like:

              The following should fix it sed 's/:N/ /' INFILE | awk '{print $1}' | sed -e 's|_1|/1|' -e 's|_2|/2|' > OUTFILE

              Comment

              • zjrouc
                Member
                • Sep 2010
                • 25

                #8
                Thanks, I will try

                Comment

                • Wallysb01
                  Senior Member
                  • Feb 2011
                  • 286

                  #9
                  Actually, you might be a little more careful and change the first sed command to:

                  sed 's/:N:/ /'

                  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
                  25 views
                  0 reactions
                  Last Post SEQadmin2  
                  Started by SEQadmin2, 06-30-2026, 05:37 AM
                  0 responses
                  23 views
                  0 reactions
                  Last Post SEQadmin2  
                  Started by SEQadmin2, 06-26-2026, 11:10 AM
                  0 responses
                  23 views
                  0 reactions
                  Last Post SEQadmin2  
                  Started by SEQadmin2, 06-17-2026, 06:09 AM
                  0 responses
                  55 views
                  0 reactions
                  Last Post SEQadmin2  
                  Working...