Covariates to be included in DE model
2
0
Entering edit mode
@0693d951
Last seen 2.5 years ago
Italy

Whenever I'm interested in comparing groups, I usually specify the design for my DESeq2/limma pipeline to include only the variables related to the contrast of interest. Should I include in the design other variables that I'm not interested in contrasting, but to "correct" the model for side effects (kinda the same you do with multivariate survival models)?

Examples could be: RIN scores for my samples or other sources of technical variation, other grouping variables that may be causally related to my comparison of interest.

DESeq2 limma • 1.0k views
ADD COMMENT
2
Entering edit mode
@mikelove
Last seen 10 hours ago
United States

This is covered in our documentation and I'm sure also in limma docs. Yes, batches should be included in general. Rather than RIN, if there is substantial technical variation, we use RUV or SVA in the lab to estimate continuous nuisance variables.

ADD COMMENT
0
Entering edit mode

Michael Love Please, do you have any suggestions regarding how to deal with the RIN scores. Do you remove low RIN scores or SVA seems to be efficient even with low RIN scores?

ADD REPLY
0
Entering edit mode

Above I indicate that I prefer SVA / RUV to just using RIN if you are keeping the sample. We use a variety of measures in the lab to detect failed samples.

ADD REPLY
2
Entering edit mode
@gordon-smyth
Last seen 2 hours ago
WEHI, Melbourne, Australia

All the relevant variables should be included in the design matrix. That's a universal principle of any anova/regression analysis in statistics, not just for limma and DESeq2. Otherwise the analysis will be underpowered or biased.

As far as technical corrections go, you should include variables only if they have an meaningful effect for your data. I hardly ever include RIN myself.

ADD COMMENT

Login before adding your answer.

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