Cutoff of reads in htseq
2
0
Entering edit mode
9.3 years ago

Hello,

To my understanding the standard number of cutoff for falsely expressed genes in trancriptome is 30 reads.

Am I right? and what is the reason for a this specific cutoff?

Thank you

RNA-Seq • 2.6k views
ADD COMMENT
0
Entering edit mode

Can you explain more ? As the heading of question, htseq, there is no min or max cutoff to calculate no. Of read/fragments mapped per genomic location. If you are talking about the differential expression, the cutoff will be based on statistical test but not on any standard number.

If you can provide any source for your understanding, that would be good.

ADD REPLY
0
Entering edit mode
9.3 years ago

There is no standard cut-off and there could never be one. The best practice is to use independent filtering.

ADD COMMENT
0
Entering edit mode
9.3 years ago
Martombo ★ 3.1k
there is no standard threshold. you can use the one that is more suitable for your data. in deseq2 you will find an implementation of the independent filtering, suggested by Devon. it basically sets the threshold in a way to get the highest number of differentially expressed calls. check it afterwards, since it could be too high (or too low), depending on your expectations.
ADD COMMENT
0
Entering edit mode

I'm not dealing with differentially expressed gene but with the transcriptome itself.

I have the reads of each gene , how do I decide which number of reads is too low to consider as a signficantly expressed gene?

ADD REPLY
0
Entering edit mode

There's no standard for that as well (there never could be). The best you can do is plot the FPKM/RPKMs and see if you have an obviously bimodal distribution. If not, you're left with using the top X% as expressed.

ADD REPLY
0
Entering edit mode

Hello Devon, can i ask you after the observing the bimodal distribution, which steps do you suggest for filtering, im dealing with tpm. Thanks in advance

ADD REPLY

Login before adding your answer.

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