SEQanswers

Go Back   SEQanswers > Bioinformatics > Bioinformatics



Similar Threads
Thread Thread Starter Forum Replies Last Post
picard error seq_GA Bioinformatics 2 07-15-2014 04:50 AM
error in picard (SAM validation error) dongshenglulv Bioinformatics 3 07-05-2013 12:58 PM
Picard FixMateInformation error? reeso123 Bioinformatics 5 06-04-2013 12:09 PM
Picard error JohnK Bioinformatics 14 12-14-2012 05:41 AM
What's the merit of running FixMateInformation yjx1217 Bioinformatics 1 12-13-2012 09:17 AM

Reply
 
Thread Tools
Old 02-07-2013, 02:33 AM   #1
oriol
Junior Member
 
Location: Lleida, Spain

Join Date: Jan 2013
Posts: 2
Default Error in flags after picard FixMateInformation?

Hi!

I am not sure, but it seems that after using Picard's FixMateInformation, some flags of the BAM file are wrong.

For instance, my initial BAM file has these two reads:

Quote:
HWI-ST731_145:7:1306:17910:58342#15@0 409 12 57997071 3 76M * 0 0 GGAGGAGATCAGCGAGAGGCTGGAAGAAGCTGGCGGGGCGACGTCAGCCCAGATTGAGATGAACAAGAAGCGCGAG DDDDDEDDDDDDDDCDDDEEEECEEDFFFGHHJJJJJJJJJIIIJIJIJJJJIIJJIJJIIJIHHHHHFFFFFCCC CC:Z:= MD:Z:30C45 RG:Z:D1126ACXX_7_15 XG:i:0 NH:i:2 HI:i:0 NM:i:1 XM:i:1 XN:i:0 XO:i:0 CP:i:58221643 AS:i:-5 XS:A:+ YT:Z:UU
HWI-ST731_145:7:1306:17910:58342#15@0 1177 12 58221643 3 76M * 0 0 GGAGGAGATCAGCGAGAGGCTGGAAGAAGCTGGCGGGGCGACGTCAGCCCAGATTGAGATGAACAAGAAGCGCGAG DDDDDEDDDDDDDDCDDDEEEECEEDFFFGHHJJJJJJJJJIIIJIJIJJJJIIJJIJJIIJIHHHHHFFFFFCCC MD:Z:30C45 RG:Z:D1126ACXX_7_15 XG:i:0 NH:i:2 HI:i:1 NM:i:1 XM:i:1 XN:i:0 XO:i:0 AS:i:-5 XS:A:+ YT:Z:UU
If I am not mistaken, the first and second reads have the flag 0x8 (i.e. next segment in the template unmapped). Furthermore, the first read has the flag 0x100 (i.e. secondary alignment). From these flags, I understand that these two alignments are the same read aligned in two different places.

After using the FixMateInformation function with this file, these two reads became:

Quote:
HWI-ST731_145:7:1306:17910:58342#15@0 433 12 57997071 3 76M = 58221643 224573 GGAGGAGATCAGCGAGAGGCTGGAAGAAGCTGGCGGGGCGACGTCAGCCCAGATTGAGATGAACAAGAAGCGCGAG DDDDDEDDDDDDDDCDDDEEEECEEDFFFGHHJJJJJJJJJIIIJIJIJJJJIIJJIJJIIJIHHHHHFFFFFCCC CC:Z:= MD:Z:30C45 RG:Z:D1126ACXX_7_15 XG:i:0 NH:i:2 HI:i:0 NM:i:1 XM:i:1 XN:i:0 XO:i:0 CP:i:58221643 MQ:i:3 AS:i:-5 XS:A:+ YT:Z:UU
HWI-ST731_145:7:1306:17910:58342#15@0 1201 12 58221643 3 76M = 57997071 -224573 GGAGGAGATCAGCGAGAGGCTGGAAGAAGCTGGCGGGGCGACGTCAGCCCAGATTGAGATGAACAAGAAGCGCGAG DDDDDEDDDDDDDDCDDDEEEECEEDFFFGHHJJJJJJJJJIIIJIJIJJJJIIJJIJJIIJIHHHHHFFFFFCCC MD:Z:30C45 RG:Z:D1126ACXX_7_15 XG:i:0 NH:i:2 HI:i:1 NM:i:1 XM:i:1 XN:i:0 XO:i:0 MQ:i:3 AS:i:-5 XS:A:+ YT:Z:UU
Now, these two reads does not have the flag 0x8. Furthermore, their RNEXT and PNEXT fields indicate that one is the mate of the other.

This behavior is correct?

Thanks in advance!
oriol is offline   Reply With Quote
Old 08-06-2013, 04:31 AM   #2
oriol
Junior Member
 
Location: Lleida, Spain

Join Date: Jan 2013
Posts: 2
Default

If someone using old Picard versions has the same issue: It was a Picard bug. The Picard team solved it very fast in newer versions.
oriol is offline   Reply With Quote
Old 05-20-2015, 12:24 AM   #3
gmarco
Member
 
Location: Spain

Join Date: Oct 2012
Posts: 36
Default

I'm experiencing weird behavior in cufflinks when using Picard tools FixMateInformation on *.bam produced by tophat2.

Using picard-tools-1.129 and cufflinks v2.2.1.

I'm not getting same results after using fixmate on tophat2 bams. I usually align with tophat2, filter by a quality score of 5 to retain only unique alignments and then fixmate bam with picard tools.

However comparing cufflinks results with and without Picard FixMateInformation make a really big difference. Results with fixmate make no biological sense at all.

Could this be the issue?
gmarco is offline   Reply With Quote
Reply

Tags
error, fixmateinformation, picard

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:25 PM.


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