DESeq2 analysis with pairwise analysis and batch effect correction
1
0
Entering edit mode
jogiles • 0
@jogiles-12736
Last seen 8.6 years ago

Hello,

I am using DESeq2 to analyze ATAC-seq data. The samples are from human patients, pre and post therapy -- so, require a paired analysis which can be done by including the donor ID in the model matrix. The samples had to be processed in 3 batches (no known variables are confounded with batch). 

My question: What is the best way to incorporate the pairwise analysis and account for batch effects? Include both in the model matrix? Does the order matter? I don't think I can remove the batch effects with Limma or Combat prior to DESeq2 because it requires raw counts as input.

Any advice would be greatly appreciated! Thank you!

Josephine

deseq2 • 3.0k views
ADD COMMENT
0
Entering edit mode
@mikelove
Last seen 17 hours ago
United States
You can simply use a design ~patient + treatment. This let's you test for after vs before treatment within each patient.
ADD COMMENT
0
Entering edit mode
Thank you for the quick response! I'm sorry if my question was unclear. I don't know the best was to account for batch effects in a pairwise design: ~ batch + patient + treatment ? Since Deseq2 requires raw counts, I assume I can't really use combat or something similar to remove batch effects prior to DESeq2?
ADD REPLY
0
Entering edit mode
Having patient in the design deals with batch, assuming the patients are nested within batch. You only make comparisons within patient so a batch effect cancels out.
ADD REPLY
0
Entering edit mode
O right! Great. Thanks so much.
ADD REPLY
0
Entering edit mode

What if patients are not nested within batches? Will the design be ~ batch + patient + treatment?

ADD REPLY
0
Entering edit mode

Thats a suboptimal design Id say. Ill answer on your other post.

ADD REPLY
0
Entering edit mode

Thanks! Talk to you there.

ADD REPLY

Login before adding your answer.

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