Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • jyli
    Member
    • Nov 2008
    • 21

    MAQ error

    I am using MAQ 0.7.1 and I recently encountered a weird errors:

    -- maq-0.7.1
    [ma_load_reads] loading reads...
    [ma_load_reads] set length of the first read as 35.
    [ma_load_reads] 17547636*2 reads loaded.
    [ma_longread2read] encoding reads... maq: read.cc:106: match_info_t* ma_longread2read(const longreads_t*): Assertion `matches' failed.

    I double checked that both query data and database data were OK. Any insight is appreciated.
  • johnwhitaker
    Junior Member
    • Jan 2009
    • 6

    #2
    I also got this error. Did you ever work out what was going wrong?

    Comment

    • gcarbajosa
      Junior Member
      • May 2009
      • 6

      #3
      maybe you are loading too many reads at the same time?

      from the maq's user manual:

      "The best way to run this command is to provide about 1 to 3 million reads as input. More reads consume more memory"

      I suggest that you split the file in smaller sets of 1 to 3 million reads as suggested. I've done it and it works faster and safer.

      Comment

      • johnwhitaker
        Junior Member
        • Jan 2009
        • 6

        #4
        I got around the problem by increasing the memory to 16 Gigs.

        Comment

        • jyli
          Member
          • Nov 2008
          • 21

          #5
          So, it is memory usage problem then? Interesting though as the developer claimed that we do NOT need to split file, which I always did in the past.

          Comment

          • erichpowell
            Member
            • Nov 2009
            • 10

            #6
            I got around the problem by increasing the memory to 16 Gigs.
            How did you increase the memory? I don't see any parameters to modify that?

            I am very interested in this solution because I have encountered this error before and in past times I was able to get past this error by reducing the number of reads I was aligning, say, from 2M to 1M. In this case, I have dropped the number of reads as low as 750,000 and still the error persists.

            Comment

            • johnwhitaker
              Junior Member
              • Jan 2009
              • 6

              #7
              I think I just specified that the job should be allowed more memory when submitting to our cluster.

              Comment

              • Brajbio
                Member
                • Jun 2010
                • 20

                #8
                I too got the similar error.

                But surprisingly when i am feeding the single read input file (.bfq) of size 2.9 GB of each read 75 bp, its running sucessfully with MAQ but when i am giving the input file (.bfq) of size 3.0 GB (each read 75 bp), i am getting the error:

                -- maq-0.7.1
                [ma_load_reads] loading reads...
                [ma_load_reads] set length of the first read as 75.
                [ma_load_reads] 82785673*2 reads loaded.
                [ma_longread2read] encoding reads... maq: read.cc:106: match_info_t* ma_longread2read(const longreads_t*): Assertion `matches' failed.
                Aborted

                I am pretty sure there is no memory problem , as i am using 64 GB RAM

                I will greatly appreciate if someone can help me out to tackle this.

                Comment

                • Brajbio
                  Member
                  • Jun 2010
                  • 20

                  #9
                  To my previous post i would like to add that......i had already successfully match this big size reads data once before with MAQ and even i have got the output as .map files, so i am pretty sure, size of reads and the memory is not the constrain to be pointed out. Still i am running the Maq with input of 2.9 GB of reads files (.bfq) having length read 75 bp each, which is processing perfectly.

                  Comment

                  • qiuyongquan
                    Junior Member
                    • Feb 2012
                    • 1

                    #10
                    Phred-like quality value

                    What does the following sentence mean?
                    "Over all the raw reads, the average Phred-like quality value at base 80 was Q26.6 and the average base position at which this declined below Q30 was 69.7."

                    How can I use maq to get Phred-like quality value?

                    Comment

                    Latest Articles

                    Collapse

                    • SEQadmin2
                      Advanced Sequencing Platforms Tackle Neuroscience’s Toughest Genomics Problems
                      by SEQadmin2



                      Genomics studies in neuroscience face a special challenge due to the brain’s complexity and scarcity of samples. Mapping changes in cell type and state using conventional next-generation sequencing methods remains challenging. Advances in technologies like single-cell sequencing, spatial transcriptomics, and long-read sequencing have opened the door to deeper studies of the brain and diseases like Alzheimer’s, amyotrophic lateral sclerosis (ALS), and schizophrenia.
                      ...
                      07-09-2026, 11:10 AM
                    • SEQadmin2
                      Cancer Drug Resistance: The Lingering Barrier to Rising Survival
                      by SEQadmin2



                      Cancer survival rates have significantly increased in the last few decades in the United States, reaching a combined 70% 5-year survival rate by 2021. Behind this number, there are years of research to find new therapies, drug targets, and early detection methods. But there is one core challenge that keeps slowing down these advances, and it’s about drug resistance.

                      There is no single reason why many patients don’t respond to treatment as expected. Cancer is...
                      07-08-2026, 05:17 AM
                    • 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

                    ad_right_rmr

                    Collapse

                    News

                    Collapse

                    Topics Statistics Last Post
                    Started by SEQadmin2, 07-09-2026, 10:04 AM
                    0 responses
                    23 views
                    0 reactions
                    Last Post SEQadmin2  
                    Started by SEQadmin2, 07-08-2026, 10:08 AM
                    0 responses
                    15 views
                    0 reactions
                    Last Post SEQadmin2  
                    Started by SEQadmin2, 07-07-2026, 11:05 AM
                    0 responses
                    33 views
                    0 reactions
                    Last Post SEQadmin2  
                    Started by SEQadmin2, 07-02-2026, 11:08 AM
                    0 responses
                    31 views
                    0 reactions
                    Last Post SEQadmin2  
                    Working...