Comparing transcriptome variation across groups after Variance stabilizing transformation using DESeq2
1
0
Entering edit mode
Bitao Qiu • 0
@bitao-qiu-14201
Last seen 5.5 years ago
Denmark/Copenhagen/Center for Social Ev…

Hi,

We would like to compare the expression variation across mulitple groups, e.g. to examine whether single cell samples in 10 hours (n = 30) have higher transcriptome variation than samples in 15 hours (n = 30). To account for the association between mean and variance in RNAseq, we first used VST to normalize the expression level for each group separately, following this document: https://rdrr.io/bioc/DESeq2/f/vignettes/DESeq2.Rmd.

After normalization with VST for each group, we find that there are difference for the overall expression variaton across groups. However, because VST estimates the mean-variance and fits the dispersal for each group separately, we are not sure whether the within-group variances are comparable among groups.

We have tried setting blind = F, fitType for all three options, and VST using one group as reference, and these methods returned similar results (while the level of difference differed). However, we feel that we need better statistical argument to make sure that the result is not the artifact of normalization.

May I ask is there any suggestion for the use of VST for multiple groups? And can we find any statistical proof (or direction of working) that this normalization method can be used for comparing variance across groups?

Best, Bitao

deseq2 vst variance • 1.0k views
ADD COMMENT
0
Entering edit mode
@mikelove
Last seen 1 day ago
United States

VST should work fine here, it estimates a simple transformation, think of it as f(x), for the entire dataset. It’s similar to log(x) but tends to have better performance than the logarithm for reasons explored in the vignette and workflow.

ADD COMMENT

Login before adding your answer.

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