Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • amcrisan
    Junior Member
    • Oct 2009
    • 9

    Mosaik assembly error

    I get the following error when running Mosaik assembler... it starts of just fine, however after finishing up the chromosome 1 I get the following error:

    - saving alignments from 10:
    ERROR: An attempt was made to get reads from an alignment archive that hasn't been opened yet.

    I supply it a sorted aligned file, and would like it output in the gigbayes format so that I can use the GigaBayes program for SNP discovery. I tried making the -f file be both ace and gig and they both provide the same error.

    Any suggestions?

    Thanks.
  • yosemite
    Junior Member
    • Oct 2009
    • 2

    #2
    Are you using colorspace (SOLiD) data?

    Comment

    • amcrisan
      Junior Member
      • Oct 2009
      • 9

      #3
      I am using Illumina..so no not colour space.

      Comment

      • jerolar
        Junior Member
        • Nov 2009
        • 2

        #4
        Hello,

        I'm new with the Mosaik package and I got the same error. Everything is fine until MosaikAssembler. I work with 454 reads and I want to assemble them on a set of reference sequences, it's a transcriptome sequencing project. Maybe it's because I have more than one reference sequences, but I see nothing special in the doc how to deal this case of figure.

        Comment

        • mack
          Junior Member
          • Oct 2009
          • 4

          #5
          i'm on the same situation as jerolar. anyone emailed the author?

          Comment

          • jerolar
            Junior Member
            • Nov 2009
            • 2

            #6
            The bug has been reported to the authors but up to now, there are no reply to this problem. We must check on the mosaik's bug tracking website and report here any useful answer. This is the ID #10:

            Comment

            • dsenalik
              Carrot Scientist
              • Nov 2009
              • 42

              #7
              I just hit the same bug, but the new version 1.0.1367 released Nov 19 appears to have
              resolved this error, it is working fine for me. I added this same info in the bug tracking website.

              Comment

              Latest Articles

              Collapse

              ad_right_rmr

              Collapse

              News

              Collapse

              Topics Statistics Last Post
              Started by SEQadmin2, 06-09-2026, 11:58 AM
              0 responses
              25 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-05-2026, 10:09 AM
              0 responses
              30 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-04-2026, 08:59 AM
              0 responses
              39 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-02-2026, 12:03 PM
              0 responses
              62 views
              0 reactions
              Last Post SEQadmin2  
              Working...