EdgeR TMM normalisation
1
4
Entering edit mode
7.5 years ago
AW ▴ 350

Hi,

I have some RNA-seq samples that I want to normalize and then output RPKM expression, and I will use the following commands from EdgeR.

expr <- DGEList(counts=data, group=conditions)
expr <- calcNormFactors(expr)

expr_norm <- rpkm(expr, log=FALSE,gene.length=vector)


I'd be very grateful if you could answer these questions.

1. When creating the expr <- DGEList(counts=data, group=conditions), what effect does specifying groups have one the TMM normalisation? How does TMM use this information and how would the results differ if you did specify groups versus not?
2. The expression data I am using was obtained from mapping reads onto denovo contigs assembled with Trinity. I then chose the most highly expressed contig from each cluster as the "best isoform" and then summed expression across all the contigs in the cluster as the expression value for that cluster. Therefore I do not have one obvious gene length to use. Should I use the longest contig from the cluster?

Thanks!

RNA-Seq normalisation rpkm TMM EdgeR • 6.8k views
ADD COMMENT
0
Entering edit mode

Any questions relating to edgeR may be best answered via the mailing list.

http://www.bioconductor.org/help/mailing-list/

If I were you I'd search the mailing list first to see if someone else has asked a similar question. If not make a post. The developer of edgeR and other R bioconductor packages are pretty active on the mailing lists.

ADD REPLY
1
Entering edit mode
7.5 years ago

calcNormFactors() doesn't use the group information. In fact, if you leave it out when making the DGEList object then every sample is given its own group. In other words, it makes no difference. The group information is used by other functions when you specify a design.

I've never used trinity, so I can't give any guidance there (perhaps make that its own question and give it an appropriate title).

ADD COMMENT

Login before adding your answer.

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