Is my data too noisy for DESeq? Should I model noise as unwanted variation?
1
0
Entering edit mode
Ben ▴ 10
@974411d6
Last seen 4 weeks ago
United Kingdom

I am trying to relate a factor (sensitivity) to gene expression. I have ~40 samples of breast cancer, each a different cell line, from a few lung cancer subtypes.

When I model my known clinical factors by variance partition to examine the variation explained from each, I see that the vast majority of my variance in gene expression is explained by unknown factors and represented by residuals. It seems my data is very noisy (which is probably to be expected as each sample comes from a different primary tumour).

My question is: should I model these residuals / noise as unwanted variation using RUV or similar? With the aim of increasing variance explained by sensitivity, separating them strongly on PCA by sensitivity, then running DESeq with these in my design formula?

Or do I have to accept that my data is too noisy for DESeq analysis and look elsewhere for markers of sensitivity?

enter image description here enter image description here

Crosspost on Biostars: https://www.biostars.org/p/9579592/

RNASeqData DESeq2 • 661 views
ADD COMMENT
0
Entering edit mode
@mikelove
Last seen 3 hours ago
United States

My question is: should I model these residuals / noise as unwanted variation using RUV or similar?

Yes. This is the way to go.

too noisy for DESeq analysis

When it's structural (explainable by RUV, SVA, etc., batch effects affecting many genes in parallel), it's perfectly fine (and appropriate) to use these factors to address the problem.

The "too noisy" category for NB GLM in my opinion is more when the data is conditionally bimodal (as happens sometimes in microbiome or other heavily PCR-ed and non-UMI corrected data).

ADD COMMENT
0
Entering edit mode

Amazing, thank you for your help!

ADD REPLY

Login before adding your answer.

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