makeHmap(mRNAdat, miRNAdat, mRNAlst, mRNAvec = NULL, miRNAvec = NULL,
chipPkg, header, plot = TRUE, out = TRUE, lhei = c(0.05, 0.95),
margins = c(5, 8))
ExpressionSet
, data.frame
or matrix
of mRNA expression values. The row.names for these data should correspond to
the manufacturer's probe ID. Currently, the only manufacturer supported is
Affymetrix.ExpressionSet
, data.frame
or matrix
of mRNA expression values. The row.names for these data should correspond to
the manufacturer's probe ID. Currently, the only manufacturer supported is
Affymetrix.list
of mRNA probe IDs where the names of each list
item are mirBase miRNA IDs. Usually this will be the output from
mirna2mrna
.NULL
, this will simply be 1:ncol(mRNAdat).NULL
, this will simply be 1:ncol(miRNAdat).heatmap.2
. This controls the ratio of the heatmap
to the key size. If there are very few mRNAs being plotted, you may need to change to
something like (0.5, 5).heatmap.2
. This controls the right and bottom
margins, respectively. Increase either value if names get cut off.TRUE
.If creating a plot, note that if the number of significant mRNA probes is
large, the resulting heatmap will have many rows and will not plot correctly
on the usual graphics device within R. In order to visualize, it is almost
always better to output as a pdf. In addition, the dimensions of this pdf
will have to be adjusted so the row names for the heatmap will be legible.
As an example, a heatmap with 10 miRNA transcripts and 100 mRNA transcripts
will likely need a pdf with a width argument of 6 and a height argument of
25 or 30. It may require some experimentation to get the correct arguments
to the pdf
function.
Also please note that this function by necessity outputs rectangular data. However, there will be many instances in which a given miRNA isn't thought to target a particular mRNA. Whenever this occurs, the heatmap will have a white cell, and the output data for that combination will be NA.