deseq2 correction batch effect without design
1
0
Entering edit mode
mdidish • 0
@mdidish-21416
Last seen 5.4 years ago

Hi

I would like to correct batch effect using deseq2, to analyze one hundred of RNA-Seq of tumors, without experimental design. 80 tumors were sequenced in 2018, and 20 in 2019; I can see a strong batch effect whent I plot PCA on reads count or on data after DESeq between 2018 and 2019 tumors.

Usualy I used:

coldata <- as.data.frame(rep(TRUE, each=100))
rownames(coldata)<- colnames(COUNT)
colnames(coldata)<- c("group")    
dds<-DESeqDataSetFromMatrix(COUNT, coldata,design=~1)

I read that DESeq can correct batch effect with this kind of command:

dds <- DESeqDataSet(COUNT, design = ~ batch + condition)

But in my case I have no condition, and I tried "design=~batch", but without effect. I can remove efficiently batch effect with ComBat, with very good result on PCA plot. But then I have negatives values in my matrix, which is a problem for further analysis.

Which solution can I try?

Thank you for any suggestion.

deseq2 batch effect • 2.8k views
ADD COMMENT
0
Entering edit mode
swbarnes2 ★ 1.4k
@swbarnes2-14086
Last seen 3 days ago
San Diego

DESeq does not correct the batch effect, it incorporates it into its linear model making. And you do that just like above, by adding batch to the design along with the other elements of the experiment.

ADD COMMENT
0
Entering edit mode

Thank you for your response. But by adding batch to the design, I still have a strong batch effect when I plot PCA with DESeq matrix. So I can't use these matrix to clustering tumors.

When I remove batch effect with ComBat, I have very good results very good result on PCA plot, but I can't use ComBat matrix because negative values.

So what solution do you recommend?

ADD REPLY
0
Entering edit mode

There’s a FAQ exactly covering your question here in the DESeq2 vignette.

ADD REPLY

Login before adding your answer.

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