I'm looking at identifying differentially expressed genes. I'm using Salmon, importing the quantification using tximport as outlined here. It's a simple comparison using infected and non-infected, and I've tried using three differential expression pieces of software (edgeR, DESeq2 and Limma).
However, for one of the conditions (there are only 2 reps), one rep is unfortunately a bit different from the other (actual gene expression). As a result, the number of DE genes is reduced and is making any biological interpretations challenging. To help with this, I'd like to use RUVSeq (RUVs), but I'm not entirely sure how to use the offsets correctly.
Although slightly different but related, I've looked at the offsets section of the EDASeq vignette, and from what I can see, theoretically I should be able to use the offsets as input into RUVSeq. I just don't want to calculate this incorrectly and end up interpreting the data wrong
Any ideas or suggestions would be greatly appreciated!
Thanks for above reply Mike - that's a cool idea which I'll use.
However, applying this to a different experimental design, this probably isn't the best way right. For example:
How does this look if I was to apply RUVs?
So, I'd need to create a model.matrix (m1 below) as outlined here and run something like this?
Thanks in advance - and apologies for all the nested questions
Why do you say the DESeq() and results() line don’t incorporate RUV factors? They do. Putting a covariate into the design is “controlling for” that covariate when estimating LFC for others.
ahh, that was me misunderstanding how the RUV factors were being incorporated into the design - clearly they are. Thanks for clarifying!
Last bit of clarification.... Which of these would you suggest as input to RUVs? I ask as I saw in the link you supplied, that when using svaseq, normalised values were passed
The SVA workflow doesn't have any steps to account for sequencing depth, hence we recommend supplying the scaled counts to SVA.
However, RUVSeq does have steps to deal with sequencing depth, see vignette section 2.1, the fourth code chunk. So if you are following the RUVSeq workflow including that step you can provide original counts, not scaled counts.
Legend - thanks Mike