Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • papori
    Senior Member
    • Dec 2010
    • 181

    bwa sampe segmentation fault

    Hi all,
    i am using bwa-0.5.9 for illumina output.

    i have reads from 2 samples of same organism.
    So i have 2 databases.

    when i run BWA on the first, everything went well. the SAM file is 3.3GB.

    On the second, i got segmentation fault in the last part, when converting to *.sam.
    it succeed to convert 2.2GB , and then seg` fault.

    My steps are:
    bwa index -a is database.fasta

    bwa aln database.fasta read_1.fastq > database_aln_sa_1.sai
    bwa aln database.fasta read_2.fastq > database_aln_sa_2.sai

    bwa sampe database.fasta database_aln_sa_1.sai database_aln_sa_2.sai read_1.fastq read_2.fastq > database_aln.sam

    When i run bwa with samse on each end separately , i got 2 sam file , each in size 1.6GB , as expected.


    My questions are:
    How can i solve the Segmentation fault?
    Or, Can i merge the 2 sam files that have been resulted separately to one sam?without loosing any data?

    Thanks in advance..
  • giorgifm
    Member
    • Aug 2011
    • 35

    #2
    Dear papori,

    my best solution at BWA segmentation fault has always been to change cpu and increase RAM. Otherwise, you may try splitting your original paired fastq files in half and try again.

    And then merge the resulting (paired) BAM files with Picard Tools MergeSamFiles

    Good luck!

    Comment

    • CompBio
      Member
      • Aug 2009
      • 26

      #3
      I'm running into a similar problem. I've got about 1 million paired-end reads (~500,000 pairs) that I'm aligning to about 6,000 transcript sequences. bwa aln works fine for both of them, but bwa sampe exits immediately with a segmentation fault, both with and without the -P option.

      I'm using the following format:
      bwa sampe -f part_1_part_2.sam transcripts.fa part_1.aln part_2.aln part_1.fq part_2.fq
      The only feedback I get is:
      Segmentation fault (core dumped)
      I'm working on a machine with 128GB memory, so I really can't imagine it's a memory issue. I've used bwa sampe successfully with similar data (500,000 pairs and 28,000 transcripts), but not with this particular data set.

      It's frustrating, to say the least.

      Comment

      • stylz2k
        Junior Member
        • Nov 2012
        • 8

        #4
        I'm having the same trouble with bwa 0.6.2. Its really frustrating.

        I have a machine with Intel Core i5 and 8 GB RAM.

        Comment

        • fongchun
          Member
          • May 2011
          • 55

          #5
          Did you guys ever find solutions to your problems of segmentation fault?

          Comment

          • CompBio
            Member
            • Aug 2009
            • 26

            #6
            In our case the problem went away when we reduced the size of the headers in the FASTA file. We were storing meta-data in the headers that sometimes grew pretty long (100's of characters). By storing the meta-data in a table and using only the indexes as FASTA headers, the problem went away.

            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, Yesterday, 05:37 AM
            0 responses
            6 views
            0 reactions
            Last Post SEQadmin2  
            Started by SEQadmin2, 06-26-2026, 11:10 AM
            0 responses
            16 views
            0 reactions
            Last Post SEQadmin2  
            Started by SEQadmin2, 06-17-2026, 06:09 AM
            0 responses
            51 views
            0 reactions
            Last Post SEQadmin2  
            Started by SEQadmin2, 06-09-2026, 11:58 AM
            0 responses
            110 views
            0 reactions
            Last Post SEQadmin2  
            Working...