Can I control the exposure time as a batch effect?
1
0
Entering edit mode
3.1 years ago
greyman ▴ 190

Hi, the experiment that I conducted consists of a control and 4 different concentrations of chemical treatments (5 replicates per treatments) under two different exposure time (12 hours and 48 hours). As I was interested to compare the expression profile between the two time points, I found out there is a batch effect caused by sequencing both time points at different batches from my PCA plots: the 12hours group has separated entirely from the 48 hours group, even for my two control groups they were also far far away from each other.

Can I therefore treat the exposure time as a batch effect in my DESeq design model? What disadvantage would there be the batch is exactly same as the exposure time? I couldn't find similar posts or suggestion as I had searched in google. Here I would like to treat the chemical concentration as a linear model

dds <- DESeqDataSetFromMatrix(counts, metadata, design = ~time + chemical.con )

DESeq(dds)

resultsNames(dds)
[1] "Intercept" "time"      "chemical.con"

Something doesn't look right here, seems like I couldn't compare the expression profiles between 8 days and 4 days, any advice?

Thank you very much

batch-effect RNA-seq time-series deseq2 • 996 views
ADD COMMENT
0
Entering edit mode

Can you provide a picture of the PCA plot? It's not clear from just your description alone whether you have a batch effect or not.

ADD REPLY
1
Entering edit mode
3.1 years ago

Can I therefore treat the exposure time as a batch effect in my DESeq design model?

Yes, treating time as a batch effect seems reasonable if your control samples are showing notable effects due to it.

What disadvantage would there be the batch is exactly same as the exposure time?

Well, you can't measure the effect of time, since it's convolved in the batch effect.

ADD COMMENT

Login before adding your answer.

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