Error in lfcShrink
1
0
Entering edit mode
@claudio_carril-24100
Last seen 4.1 years ago
University of Liège, Belgium

Dear community I am writing to you because I have a problem with DESEq2 when I try to use lfcShrink. After that, it is not possible to continue with the analysis

This error started to happen when I run my analysis in Ubuntu 20.04.1 and use R 4.0.3, when I ran the same analysis in the previous version of R there was not a problem

The line:

> resShrunk <- lfcShrink(dds, contrast = c("condition", "3N_D", "20C_G2"), cooksCutoff=F)

An the error:

> resShrunk <- lfcShrink(dds, contrast = c("condition", "3N_D", "20C_G2"), cooksCutoff=F)
Error in lfcShrink(dds, contrast = c("condition", "3N_D", "20C_G2"), cooksCutoff = F) : 
  type='apeglm' shrinkage only for use with 'coef'

Thanks in advance

lfcShrink DESeq2 • 3.4k views
ADD COMMENT
1
Entering edit mode

You can either use coef or you can switch back to type="normal' which was the previous default value for type.

The reason why it depends on the version, is that type="normal" was deprecated over two release cycles, and now is no longer default (this was printed as a message to the console for two releases, before the change was made). It performs worse than apeglm/ashr. Changes are documented here. See description of shrinkage estimators in the vignette for more details.

ADD REPLY
0
Entering edit mode

Thank you so much for your help!

Now it is working properly

Best regards

ADD REPLY
1
Entering edit mode
tcalvo ▴ 100
@tcalvo-12466
Last seen 18 months ago
Brazil

Hello, Claudio.

lfcShrink does not support apeglm + contrast. You should use the coef argument instead of contrast when using apeglm. This will solve your issue.

ADD COMMENT
0
Entering edit mode

Thank you, I see that

But that with that I have more question about how to modify the coef to use the apeglm. Because, the coef it does not give me the combinations I am looking for

but for that I am going to open another question in the forum

best regards

ADD REPLY
0
Entering edit mode

Sorry, been absent from here. Did you find a solution? I usually just change the levels of my factor variable, usually the base level to solve the issue. Probably there are better ways to do it.

ADD REPLY

Login before adding your answer.

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