use gff3 file with featureCount
Entering edit mode
8.9 years ago
bakeronit ▴ 10

I use tophat do the mapping and get .bam file. I try to use featureCount. Here are some question about my data:

  1. I use paired-end reads also single-end reads in tophat, so the mapping result contain both.Which arguments I should use?
  2. My annotation file is gff3 but I check the parameter in featureCounts such as -g (GTF.attrType), I find almost everyone use -g gene_id. And gff3 use ID= and parent=. I can't get any result with my gff3 file so I convert it to gtf. Now I get read count, is it reliable? or how to deal with gff3?

Here is my command usage:

featureCounts -a my.gtf -t exon -g gene_id -o counts.txt accepted_hits.bam


RNA-Seq • 8.9k views
Entering edit mode

Hi bakeronit,

For your second point, as long as the format conversion is reliable, the information in your annotation files is the same. Your read count is correct. There would be a problem if the GFF3 and GTF file had had a different information. A format good format conversion does not modify the information in a file.

I have never been in the situation described in your first point. I'll let someone else answer.

Entering edit mode
8.8 years ago

Hi bakeronit-

Regarding your first point, on the TopHat manual page:

TopHat can align reads that are up to 1024 bp long, and it handles paired-end reads and unpaired reads at once, but we do not recommend mixing different types of reads in the same TopHat run.

After this warning, they explain how to combine your single-end and paired-end reads, in a manner.

To your second point, the Cufflinks utility gffread can convert between gff and gtf formats. I believe I've only gone gtf-to-gff, but I bet it works well in the other direction. The additional advantage is that it removes extraneous lines (extraneous to cufflinks), so you will end up with a much more compact annotation file.


Login before adding your answer.

Traffic: 1037 users visited in the last hour
Help About
Access RSS

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

Powered by the version 2.3.6