question about output of edgeR
1
0
Entering edit mode
Son Pham ▴ 60
@son-pham-6437
Last seen 9.4 years ago
United States
Dear edgeR community: In the output of edgeR for two groups testing: topTags(et, n=20), for example. We have: Gene ID logFC logCPM pValue FDR I wonder why we only have one column of logCPM, since this is a comparison, I think there should be two such columns, one for each sample? Probably that I misunderstood something here? Thanks, Son. [[alternative HTML version deleted]]
edgeR edgeR • 4.9k views
ADD COMMENT
0
Entering edit mode
@james-w-macdonald-5106
Last seen 4 days ago
United States
Hi Son, The logCPM is just the overall log average over both groups. So you have the logFC, which tells you how different the two groups were, and the logCPM which tells you the average abundance, which is a way to assess the signal/noise ratio. In other words, the larger the logCPM, the more signal you have and consequently the less influence of noise. Best, Jim On Wednesday, April 09, 2014 2:15:52 PM, Son Pham wrote: > Dear edgeR community: > In the output of edgeR for two groups testing: > topTags(et, n=20), for example. > We have: > Gene ID logFC logCPM pValue FDR > > I wonder why we only have one column of logCPM, since this is a comparison, > I think there should be two such columns, one for each sample? > > Probably that I misunderstood something here? > Thanks, > Son. > > [[alternative HTML version deleted]] > > _______________________________________________ > Bioconductor mailing list > Bioconductor at r-project.org > https://stat.ethz.ch/mailman/listinfo/bioconductor > Search the archives: http://news.gmane.org/gmane.science.biology.informatics.conductor -- James W. MacDonald, M.S. Biostatistician University of Washington Environmental and Occupational Health Sciences 4225 Roosevelt Way NE, # 100 Seattle WA 98105-6099
ADD COMMENT

Login before adding your answer.

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