Question: DEseq2: Why low counts mean count < 804
0
gravatar for lihongfei93
5 weeks ago by
lihongfei930 wrote:

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 • 70 views
ADD COMMENTlink modified 5 weeks ago by Michael Love23k • written 5 weeks ago by lihongfei930
Answer: DEseq2: Why low counts mean count < 804
0
gravatar for Michael Love
5 weeks ago by
Michael Love23k
United States
Michael Love23k wrote:

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 COMMENTlink written 5 weeks ago by Michael Love23k

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 REPLYlink written 4 weeks ago by lihongfei930

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

ADD REPLYlink written 4 weeks ago by Michael Love23k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 254 users visited in the last hour