Question: Same Rnaseq Samples Give Different Fpkm Values When Run Against Different Samples
0
gravatar for Elwood Linney
4.8 years ago by
Elwood Linney180
Elwood Linney180 wrote:
Hello, I am sure this has come up before and maybe I missed the answer. If in using cuffdiff I run a sample 1(3 repeats) vs a sample 2 and then run the same sample 1(3 repeats) against a sample 3 or a sample 4, I get different value for fpkm from sample 1 each time. Is there something going wrong here or is there something in the program that causes this difference? I have seen this with online Galaxy and with the instance I have on my Mac Pro el linney Duke University
galaxy • 2.1k views
ADD COMMENTlink modified 4.8 years ago by Jennifer Hillman Jackson25k • written 4.8 years ago by Elwood Linney180
0
gravatar for Jennifer Hillman Jackson
4.8 years ago by
United States
Jennifer Hillman Jackson25k wrote:
Hi Dr. Linney, The values for FPKM are relative to each experiment: the set of transcripts/genes assembled and evaluated, the normalization methods used. For example, when different samples are input, a different set of isoforms per gene can result from the assembly. The manual, FAQ, and 'how it works' help to explain in more detail, but in short, this is expected with many of the ways that these tools are used. Any assembly or normalization method, that impacts the FPKM calculation, is a factor. http://cufflinks.cbcb.umd.edu Running all the samples together is one option, to have values on the same relative scale. Or, if you wanted to skip discovery, and you have a reference annotation file to use as the "truth" assembly (best), this simplified protocol might be a fit for you: http://cufflinks.cbcb.umd.edu/tutorial.html#differential Hopefully this helps! Others are welcome to post comments/more suggestions, Jen Galaxy team -- Jennifer Hillman-Jackson http://galaxyproject.org
ADD COMMENTlink written 4.8 years ago by Jennifer Hillman Jackson25k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 169 users visited in the last hour