HEATMAP based on DEG data
1
0
Entering edit mode
10 months ago
hellokwmin • 0

Hello,

I have transcriptome data comprised of three treatments: Control, cold stress, and drought stress.

I performed DEG analysis by comparing cold stress vs. Control (called as cold) and drought stress vs. Control (called as drought)

Using DEG dataset, I subsequntly conducted GO enrichment analysis. One of GO terms for biological process was (lets say) was cell wall biogenesis in cold DEG, and there are 10 genes belonging to this term. So, I extracted these 10 genes to compare the level of gene expression with drouhgt DEG.

But, in drought DEG set, only 5 genes are duplicated; probably other 5 genes I can find in raw dataset. My question is:

If I want to make a heatmap to compare 10 genes between cold and drought, should I mark 5 genes (which is not detected in drought DEG) as "NA" (so in scale bar the value might be expressed as 0)? ---- in this case, I only am using DEG dataset, not raw dataset.

or,

should I extract these 10 genes from rawdata and then, chage these raw values to log2_transformed value for presenting them? ---in this case, I can get information of intrested genes from GO analysis, but to draw heatmap, I can use raw dataset.

heatmap DEG • 590 views
ADD COMMENT
0
Entering edit mode

I do not understand what you consider "DEG dataset", you should go with normalized counts and calculate z-scores to draw your heatmap

ADD REPLY
0
Entering edit mode
10 months ago
rfran010 ▴ 900

It sounds like you did "cold stress vs. Control" and "drought stress vs. Control" as separate DEG datasets (assuming a DEG dataset includes normalized counts and subsequent differential expression values).

I believe you should re-do your DEG dataset with all conditions together. This shouldn't drop any genes that are detected in at least one condition. Then use z-scores of normalized counts as suggested by @Basti.

ADD COMMENT

Login before adding your answer.

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