DEseq results -- foldchange is 0/inf
1
0
Entering edit mode
4.8 years ago
Nan ▴ 10

So after feature counts of RNA-seq bam file, I have an count file. I input the count file into DEseq, and got results which contain foldchange values such as 0/inf/NA, so how can I deal with these values when I want to use foldchange to filter out most up-/down- regulated genes?

So for foldchange == NA, I think this case can directly dropped. But what about foldchange ==0/inf?

Thank you.

id          baseMean  baseMeanA       baseMeanB  foldChange  log2FoldChange  pval      padj
SOCS4       1834      2321            1348       0.580       -0.7844         0.00038   0.844
NPIPA3      34.1155   68.23175774754  0          0           Inf             7.51E-09  7.71E-05
AL627309.5  2.0225    0               4.045      Inf         Inf             0.434     1
AP002833.2  0         0               0          NA          NA              NA        NA
RNA-Seq DEseq • 3.1k views
ADD COMMENT
0
Entering edit mode

Please use the formatting bar (especially the code option) to present your post better. You can use backticks for inline code (`text` becomes text), or select a chunk of text and use the highlighted button to format it as a code block. I've done it for you this time.
code_formatting

P.S.: You can also pretty print tabular text using column, as shown here.

ADD REPLY
1
Entering edit mode
4.8 years ago
Chirag Parsania ★ 2.0k

Hi,

Inf and NA occurred due to 0 in one of the sample (baseMeanA or baseMeanB). The common practice to deal with this problem is to add small number (e.g. 0.1 ) to normalised expression value (e.g basemean/FPKM/RPKM) and recalculate the fold change.

ADD COMMENT
0
Entering edit mode

Yes, this is a way to avoid 0/inf values. But I was worried if it is biologically reasonable?

ADD REPLY
0
Entering edit mode

It should be ok as you are adding small constant value to all the genes. Therefore, it nullifies any possibility of bias.

ADD REPLY

Login before adding your answer.

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