Go Back   SEQanswers > Bioinformatics > Bioinformatics

Similar Threads
Thread Thread Starter Forum Replies Last Post
BWA-MEM and X0/X1/etc flags mturchin20 Bioinformatics 5 07-15-2015 07:54 AM
Odd bwa-mem alignment myronpeto Bioinformatics 16 03-12-2015 12:40 PM
bwa mem -R option dakin Bioinformatics 2 05-02-2013 08:42 AM
bwa 0.6.1-r104 segfault problem rwhet052 Bioinformatics 4 10-30-2012 06:23 AM
bwa bwasw .....segmentation fault Josim Bioinformatics 0 04-26-2012 01:53 AM

Thread Tools
Old 06-13-2013, 04:17 AM   #1
Junior Member
Location: Moscow, Russia

Join Date: Nov 2012
Posts: 8
Default bwa mem segfault; bwa bwasw breaks MarkDuplicates

I have run into various problems with various versions of bwa
1. bwa mem gives a segmentation fault right away. Not sure how to debug that, no matter what memory (we have 48G) and thread settings. Has anyone else run into this problem?
The call to bwa is
bwa-0.7.5a/bwa mem -M -R "@RG\tID:$ID\tLIB:SeqCapEZ.v3\tID:$ID\tPL:ILLUMINA" -t 24 ucsc.hg19.fasta $READS1 $READS2 > $ALN_OUT.sam

2. bwasw produces a file which does no work with MarkDuplicates.
The call to bwa is
/old_home/enabieva/bwa-0.7.5a/bwa mem -M -R "@RG\tID:$ID\tLIB:SeqCapEZ.v3\tID:$ID\tPL:ILLUMINA" -t 24 ucsc.hg19.fasta $READS1 $READS2 > $ALN_OUT.sam

The MarkDuplicates error is:
Exception in thread "main" net.sf.picard.PicardException: Value was put into PairInfoMap more than once. 1: null:HWI-ST992:135:C0YGDACXX:2:1108:12651:98485

Grepping for that read brings up the following:
HWI-ST992:135:C0YGDACXX:2:1108:12651:98485 113 chr1 564775
0 43S47M chr2 55113029 0TATCGTC
AS:i:47 XS:i:47 XF:i:1 XE:i:1 NM:i:0
HWI-ST992:135:C0YGDACXX:2:1108:12651:98485 113 chr1 566621
0 51M39S chr2 55113029 0TATCGTC
AS:i:51 XS:i:51 XF:i:1 XE:i:1 NM:i:0
HWI-ST992:135:C0YGDACXX:2:1108:12651:98485 145 chr2
55113029 168 90M * 0 0TGAGCCA
AS:i:90 XS:i:0 XF:i:3 XE:i:2 NM:i:0

So it seems that the problem is that the first read is mapped twice, but this is not marked in any way.

I found a discussion of this problem, but the suggested solution seems roundabout.
Does anyone else encounter this?


Last edited by ElenaN; 06-13-2013 at 04:24 AM. Reason: bad hyperlink format
ElenaN is offline   Reply With Quote
Old 06-29-2013, 10:40 PM   #2
Junior Member
Location: China

Join Date: Jun 2013
Posts: 1

Yes, I met exactly the same error with you. Although I used the -M option, it seems also not compatible well with picard. I'm looking forward to an effective solutions.

Last edited by Zengquan; 06-29-2013 at 10:44 PM.
Zengquan is offline   Reply With Quote
Old 06-30-2013, 11:23 PM   #3
I like code
Location: San Diego, CA, USA

Join Date: Sep 2009
Posts: 438

As far as I know the picard people are working with the bwa people to get the two programs to be more compatible. BWA MEM 0.7.4 should still work. The -M option is going to be gone and instead they are going to use a new flag which will have to be picked up by samtools and picard - but like I said they are all working together on this. I can't explain the seg-fault but I do know that the latest version of MEM has done away with what the -M option used to do. If you back up to a previous version of MEM it should still work. I'm using '0.7.4-r389-beta' and it mostly works. The bwa aln/sampe pipeline is broken in that it fails to properly annotate the 'XA' field of the alignments which triggers a bug in samtools if you attempt to run those alignments through it. However, that version's 'MEM' works perfectly for me (on Mac and Linux).
/* Shawn Driscoll, Gene Expression Laboratory, Pfaff
Salk Institute for Biological Studies, La Jolla, CA, USA */
sdriscoll is offline   Reply With Quote

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 02:53 AM.

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