DEseq2: Why low counts mean count < 804
1
0
Entering edit mode
@lihongfei93-20036
Last seen 5.7 years ago

Hi, When launching the DESeq function, I get results like this:

res<- results(dds, name="genotypeA.treatment2")

summary(res)

out of 20717 with nonzero total read count adjusted p-value < 0.1 LFC > 0 (up) : 154, 0.74% LFC < 0 (down) : 7, 0.034% outliers [1] : 5, 0.024% low counts [2] : 15258, 74% (mean count < 804) [1] see 'cooksCutoff' argument of ?results [2] see 'independentFiltering' argument of ?results

My question is why low counts mean count <804?

deseq2 • 911 views
ADD COMMENT
0
Entering edit mode
@mikelove
Last seen 2 days ago
United States

That's the independent filtering (see vignette), which here is jumping over many genes with mean counts < 800. I wonder if you are using a current version of DESeq2, because we've tried to mitigate that behavior in recent versions. It can still happen though, it just means that there were few significant genes with counts < 800. I would however prefer to turn off independent filtering in this case (or use IHW, see example in vignette).

ADD COMMENT
0
Entering edit mode

Thanks for your reply. I got 439 DEGs by subset res with padj < 0.05 when I didn't turn off independent filtering. But why I got 348 DEGs when I turn it off? shouldn't it be more DEGs when I turn off independent filtering?

ADD REPLY
0
Entering edit mode

See the paper and the vignette again. The independent filtering is used to increase power (generate more DEGs).

ADD REPLY

Login before adding your answer.

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