DESeq2 with paired data Heatmap
1
0
Entering edit mode
@lweissenburgermoser-10870
Last seen 7.9 years ago

Is there a way to make a heatmap using DESeq2 for paired data? I am comparing the lung microbiome with the mouth microbiome in 33 patients And also comparing the lung microbiome over two time points (again paired data).

My OTU table was loaded into R:

otu=import_biom('C:\Users\OneDrive\otu_table.biom')

and my sort of "map" file which just contains SampleID, Location, and Paired. For example:

SampleID  Location   Paired
1_L           Lung           1
1_M          Mouth         1
2_L           Lung           2
2_M          Mouth         2

map=read.csv('C:\Users\OneDrive\Mouth vs lung R map_adj.csv',header=T,row.name=1,stringsAsFactors=F)

Again my data is paired and I want to compare the lung vs the mouth (location) using a heatmap. I've been having trouble with R. And then again with time (baseline vs later) (baseline vs x number of months later).

Thanks!

deseq2 heatmap • 1.6k views
ADD COMMENT
0
Entering edit mode
@steve-lianoglou-2771
Last seen 14 months ago
United States

Not sure what exactly you're looking for, but you can annotate rows and columns of heatmaps to get a visual of how these covariates (location, pair, etc) migrate w/ your clusters.

There are many, many, many packages that provide ways to generate heatmaps. A recent arrival on the scene (~ 1 year old) is the ComplexHeatmap package, which allows you to do pretty much everything you might want with a heatmap. Read through the vignettes to get some inspiration.

ADD COMMENT
1
Entering edit mode

Yes and to tag on to Steve's answer, we show how to make heatmaps in the DESeq2 vignette:

vignette("DESeq2")

and in the workflow:

http://www.bioconductor.org/help/workflows/rnaseqGene/

ADD REPLY
0
Entering edit mode

Thank you for your help!  I will look into these resources.

ADD REPLY

Login before adding your answer.

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