How to add FPKM values in cells of heatmap?
0
0
Entering edit mode
6.7 years ago
Mehmet ▴ 820

Dear All,

I want to add FPKM values into cells of heatmap using complex heatmap package. I made a heatmap, I tried to use:

cell_fun = function(j, i, x, y, width, height, fill) {grid.text(sprintf("%.1f", df[i, j]), x, y, gp = gpar(fontsize = 10))},

df= my data matrix having FPKM values of each gene in each sample.

Some values are seen in cell, while others are different from df file.

RNA-Seq R rna-seq • 1.6k views
ADD COMMENT
0
Entering edit mode

I already figured out.

ADD REPLY
1
Entering edit mode

For the solution:

the data frame that has FPKM values of each gene must have only FPKM values of each gene in each sample/condition. Previously, I kept gene name in the data frame, but order of FPKM values in cells of heatmap was different that the data frame.

ADD REPLY
0
Entering edit mode

Great, can you paste the solution for everyone else? I, only now, just saw your request in the other question (I was traveling today)

ADD REPLY
0
Entering edit mode

Hi Kevin,

I would like to have your opinion about differential gene expression analysis workflow;

I have ~50 genes and have RNA reads obtained from four tissues. I want to see expression differences of those genes in the four tissues. I am planning to perform the steps after quality control: 1. Alignment of each RNA reads to reference genome separately. This will produce 4 .bam files. 2. Read counting of four .bam files. in this step, should I combine all bam files or should I do read counting for each .bam files separately? 3. Normalization. Which method do you recommend? 4. DEG analysis; edgeR or DESeq.

is my workflow suitable?

ADD REPLY
0
Entering edit mode

Hello Mehmet, which read counting method do you plan to use? For normalisation, my preference is DESeq2.

Your sample size is just 4?, that is, 1 sample per tissue?

ADD REPLY

Login before adding your answer.

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