Why run FeatureCounts after Stringtie? (Galaxy recommends!)
1
3
Entering edit mode
2.9 years ago
c_u ▴ 480

Hi,

I have RNA-Seq data from patients, and I want to find novel transcripts that are differentially expressed in the treatment condition. For this, I followed the methodology given in this Galaxy tutorial - https://galaxyproject.org/tutorials/nt_rnaseq/. Here they use HISAT for mapping, followed by Stringtie for transcript reconstruction (using Stringtie allows them to find novel transcripts), and then use FeatureCounts for counting the number of reads per transcript. Then they use DESeq2 for differential expression analysis.

My question is that since Stringtie itself also gives the count (in terms of coverage, FPKM and TPM) for each transcript that it constructs, then why should I use FeatureCounts for these constructed transcripts?

RNA-Seq • 3.0k views
1
Entering edit mode

DESeq2 requires raw counts, which featureCounts provides.

3
Entering edit mode
2.9 years ago

There is absolutely no reason to do that. Actually you should rather use StringTie's quantification since that is more accurate than featureCounts - you can read more about such considerations here. Acutally DEXSeq directly supports analysis of StringTie data via tximport::tximport() as described here - although they actually don't mention StringTie in the DESeq2 vignette tximport does support StrigTie as describe here.

0
Entering edit mode

Hi Kristoffer, did you mean DESeq or DEXSeq?