\HeaderA{GO2heatmap}{Compute a heatmap for the specified data, for either a GO
category or a KEGG pathway.}{GO2heatmap}
\aliasA{KEGG2heatmap}{GO2heatmap}{KEGG2heatmap}
\aliasA{KEGG2heatmap,character,eSet,character-method}{GO2heatmap}{KEGG2heatmap,character,eSet,character.Rdash.method}
\aliasA{KEGG2heatmap,character,matrix,character-method}{GO2heatmap}{KEGG2heatmap,character,matrix,character.Rdash.method}
\keyword{manip}{GO2heatmap}
\begin{Description}\relax
For a given GO category or KEGG pathway, all probes in the supplied
data are mapped to the pathway and a heatmap is produced.
\end{Description}
\begin{Usage}
\begin{verbatim}
GO2heatmap(x, eset, data, ...)
KEGG2heatmap(x, eset, data, ...)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{x}] The name of the category or pathway. 
\item[\code{eset}] An \code{exprSet} providing the data. 
\item[\code{data}] The name of the chip.
\item[\code{...}] Additional parameters to pass to \code{heatmap}. 
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
For the given pathway or GO category all matching probes are
determined, these are used to subset the data and \code{heatmap} is
invoked on that set of data. Extra parameters can be passed through to
\code{heatmap} using the \code{...} parameter.
The \code{annotation} slot of the \code{eset} argument is used to
determine the appropriate annotation data to use.
\end{Details}
\begin{Value}
The value returned by \code{heatmap} is passed back to the user.
\end{Value}
\begin{Author}\relax
R. Gentleman
\end{Author}
\begin{SeeAlso}\relax
\code{\LinkA{heatmap}{heatmap}}
\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
 if( require("hgu95av2") ) {
  data(sample.ExpressionSet)
  KEGG2heatmap("04810", sample.ExpressionSet, "hgu95av2")
 }
\end{ExampleCode}
\end{Examples}