SEQanswers

Go Back   SEQanswers > Bioinformatics > Bioinformatics



Similar Threads
Thread Thread Starter Forum Replies Last Post
BWA Alignment Segmentation Fault adkostic Bioinformatics 24 09-09-2013 12:52 AM
bwa samse segmentation fault xguo Bioinformatics 78 05-03-2013 10:31 AM
segmentation fault in BWA sampe papori Illumina/Solexa 0 07-28-2011 08:12 AM
bwa aln Segmentation fault DNAjunk Bioinformatics 4 03-02-2011 06:28 AM
BWA Segmentation Fault (aln) raela Bioinformatics 0 05-18-2010 06:41 AM

Reply
 
Thread Tools
Old 07-28-2011, 02:28 AM   #1
papori
Senior Member
 
Location: berd

Join Date: Dec 2010
Posts: 181
Default 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..
papori is offline   Reply With Quote
Old 10-17-2012, 03:01 PM   #2
giorgifm
Member
 
Location: Columbia University Medical Center

Join Date: Aug 2011
Posts: 35
Default

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!
giorgifm is offline   Reply With Quote
Old 11-18-2012, 08:13 AM   #3
CompBio
Member
 
Location: Bristol, UK

Join Date: Aug 2009
Posts: 26
Default

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:
Quote:
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:
Quote:
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.
CompBio is offline   Reply With Quote
Old 11-19-2012, 03:07 AM   #4
stylz2k
Junior Member
 
Location: Germany

Join Date: Nov 2012
Posts: 8
Default

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.
stylz2k is offline   Reply With Quote
Old 09-21-2013, 08:44 AM   #5
fongchun
Member
 
Location: Vancouver, BC

Join Date: May 2011
Posts: 55
Default

Did you guys ever find solutions to your problems of segmentation fault?
fongchun is offline   Reply With Quote
Old 09-22-2013, 10:05 PM   #6
CompBio
Member
 
Location: Bristol, UK

Join Date: Aug 2009
Posts: 26
Default

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.
CompBio is offline   Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off




All times are GMT -8. The time now is 10:45 PM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
Single Sign On provided by vBSSO