Non-integer counts from tximport OK for edgeR / DESeq2?
Entering edit mode
Jenny Drnevich ★ 2.0k
Last seen 19 days ago
United States

Hi all,

I'm starting to use the tximport package to pull in salmon output for statistical analysis and I just wanted to verify that it is fine to use the non-integer counts with edgeR and DESeq2. Years ago, we needed to round the decimal counts from e.g., cuffdiff, but the tximport vignette implied the non-integer values were fine because there was no mention of rounding. I searched the support site and found these: C: Can I feed TCGA normalized count data to EdgeR for differential gene expression and non-integer counts for edgeR, the first of which has Steve Lianoglou asking for a separate post to highlight the qualified yes answer in regards to non-integer counts for edgeR now. That's mainly what this post is doing, and also linking it to the tximport package as more people should now be using it to pull in counts and length offsets from kallisto/sailfish/salmon/RSEM.

BTW - thanks for the great tximport package and the F1000 article on how transcript-level estimates improve gene-level inferences:!


tximport edgeR DESeq2 • 5.2k views
Entering edit mode

Thanks for posting this and tying those two threads together! To be honest I completely forgot about that comment ... which is why I guess I was hoping we could "pin" it somewhere :-)

Entering edit mode
Last seen 4 days ago
United States

hi Jenny,

Yes the examples in the tximport vignette show the intended downstream usage.

edgeR has support for non-integer counts, and the tximport-to-DESeqDataSet constructor function just rounds the estimated non-integer counts to integers. I'm not worried about any loss of precision for inference of log fold change in this rounding, because fractions of counts are tiny compared to the sampling and biological variation on counts in RNA-seq.


Login before adding your answer.

Traffic: 323 users visited in the last hour
Help About
Access RSS

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6