Incompatibility between bbmap and htseq?
2
0
Entering edit mode
8.1 years ago
fhsantanna ▴ 610

I would like to count rnaseq mapped reads on a bacterial genome. Firstly I aligned the reads using bbmap with the command: bbmap.sh ref=P_riograndensis_LN831776.fas in=A1_trim.fastq out=A1_bbmap.sam

However, when I try to count the mapped reads with htseq (htseq-count -i locus_tag -t gene A1_bbmap.sam P_riograndensis_LN831776.gff), the following error occurs: "("Illegal CIGAR string '48='", 'line 5 of file A1_bbmap.sam')"

Here is the line 5 of A1_bbmap.sam. ASFH0:01510:12713 0 LN831776 LN831776 Paenibacillus riograndensis SBR5 genome assembly SBR5(T) ,chromosome : I. 81663 3 48= * 0 0 TGAGAAGCCGGAGCCGCAGCGAAAGCGAGTCTGAATAGGGCGACTGAG ??>;;6;<6<7@@<7<><>=<>=4<=><=<===?7><;;4;;<<;;;; XT:A:R NM:i:0 AM:i:3

I believe something is wrong with bbmap sam output. But I could not realize what is the problem. Maybe the "=" signal is not expected?

bbmap htseq • 2.4k views
ADD COMMENT
5
Entering edit mode
8.1 years ago
GenoMax 141k

@fhsantanna: You won't have to do your alignments again (since that could take time). Instead you can use reformat.sh from BBMap which can use the "sam=1.3" flag for converting "="/"X" symbols to "M" to reformat your existing BAM file. This was based on some discussion about this with @Brian late last year.
BTW: This "incompatibility" also applies to featureCounts (post #140) which does not support those tags. I am not sure if a new version has been released since.

ADD COMMENT
4
Entering edit mode
8.1 years ago
michael.ante ★ 3.8k

Hi fhsantanna,

you need to set the parameter sam=1.3 during mapping with bbmap in order to have the sam version which is needed for htseq. In sam v 1.4 you can distinguish in the cigar string between match and missmatch, in version 1.3 you only see "M" as a (miss)match.

Cheers, Michael

ADD COMMENT

Login before adding your answer.

Traffic: 1781 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6