This is a test version of Biostars. For the public version, visit https://www.biostars.org.
How does DESeq2 calculate FPKM values when gene lengths are not supplied?

Hi,

I have a table of FPKM values generated by DEseq2, and I'm trying to find out what DEseq2 uses as gene lengths when these are not supplied (I'm trying to assess to what extent my results are likely to change by supplying these).

According to the manual, "feature length is calculated from the rowRanges of the dds object, if a column basepairs is not present in mcols(dds). The calculated length is the number of basepairs in the union of all GRanges assigned to a given row of object, e.g., the union of all basepairs of exons of a given gene."

Does that mean DEseq2 directly uses the ranges obtained by using rowRanges(dds)? I'm comparing these values to those obtained using the function getGeneLengthAndGCContent from the EDAseq package. The rowRanges values from DEseq2 are sometimes very close to those obtained with EDAseq, but sometimes they differ by a factor of 10. Can someone explain to me how this discrepancy is caused? Or am I simply looking at the wrong values?

Thank you, Best wishes, Hasse

rna-seq fpkm deseq2
• 1,716 views • link
updated by Kevin Blighe Kevin Blighe • written by hasse.bossenbroek • hasse.bossenbroek

Thanks for your answer, but that answer only says "(Although if you do the fragment counting with the summarizeOverlaps() function, this information is included as rowRanges and we have a function fpkm() which will do the calculation for you.)"

What happens if fragments have not been counted with summarizeOverlaps()?

• 0 views • link
written by hasse.bossenbroek • hasse.bossenbroek

0 answers

No answers yet.

Log in to answer this question.

More posts like this