warning message after HTSeq
0
0
Entering edit mode
7.1 years ago
BioDH ▴ 10

I have analyzed RNA-seq data with HTSeq.

My command that I used is

python -m HTSeq.scripts.count -f bam -r pos -s reverse -t ORF -i group -m union input.bam my.gff > output.txt

Warning message is

Warning: Mate records missing for 3752 records; first such record: <SAM_Alignment object: Paired-end read 'K00198:150:HGYHGBBXX:6:2219:20435:16049' aligned to chrII:[2341669,2341744)/+>.
11597356 SAM alignment pairs processed.

Do I have to concern the message? What does it mean?

RNA-Seq software error HTSeq • 3.4k views
ADD COMMENT
1
Entering edit mode

Is it only me that is confused, because DESeq2 is a BioC package. What command are you running there? Anyway, you are missing mate reads, where the read1 is probably flagged as paired. Probably you did any filtering (MAPQ maybe) where one of the two mates got removed. If that bothers you, you can use samtools fixmate to update the flags. Input would be a name-sorted bam file.

ADD REPLY
0
Entering edit mode

Sorry. I have changed the title.

Yes, that is not DESeq2.

I just got the reads using HTSeq module of puthon.

ADD REPLY
0
Entering edit mode

Hello BioDH,

Can you confirm that you are working with Pair-end data? This warning is telling that for 3752 reads of your BAM file, one of the two reads of the pair if missing. You should consider checking the program that gives you the BAM file. Or, you can skip this warning if you think that 7K reads of 11597k reads is negligible.

ADD REPLY
0
Entering edit mode

I'm sure that is paired-end data.

ADD REPLY
0
Entering edit mode

Hello, I have this warning, is it very serious?

Warning: Mate records missing for 2 records; first such record: <SAM_Alignment object: Paired-end read 'SRR21488088.572155' aligned to 10:[80575814,80575871)/->. 5855076 alignment record pairs processed.

ADD REPLY
0
Entering edit mode

What did you do prior to running htseq count?

ADD REPLY

Login before adding your answer.

Traffic: 2019 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