\HeaderA{gAskAncestorMessage-class}{Class "gAskAncestorMessage": A class to represent a question asking for
data from an ancestor model}{gAskAncestorMessage.Rdash.class}
\aliasA{from,gAskAncestorMessage-method}{gAskAncestorMessage-class}{from,gAskAncestorMessage.Rdash.method}
\aliasA{from<-,gAskAncestorMessage-method}{gAskAncestorMessage-class}{from<.Rdash.,gAskAncestorMessage.Rdash.method}
\aliasA{mData,gAskAncestorMessage-method}{gAskAncestorMessage-class}{mData,gAskAncestorMessage.Rdash.method}
\aliasA{mData<-,gAskAncestorMessage-method}{gAskAncestorMessage-class}{mData<.Rdash.,gAskAncestorMessage.Rdash.method}
\aliasA{type,gAskAncestorMessage-method}{gAskAncestorMessage-class}{type,gAskAncestorMessage.Rdash.method}
\aliasA{type<-,gAskAncestorMessage-method}{gAskAncestorMessage-class}{type<.Rdash.,gAskAncestorMessage.Rdash.method}
\keyword{classes}{gAskAncestorMessage-class}
\begin{Description}\relax
gAskAncestorMessage is a class to ask for model data from an ancestor model
(MVC).  For example, if a user wants to create a child model, but needs data
from both its parent and its grandparent model.  Then when the parent model
creates the new child model it would ask its parent (the grandparent of the
new child model) for data using this class.  

A specific example is if the original model contains microarray expression
data and a child model of this model is the GO graph.  Then if the user
wants to look at the expression data of only genes annotated at a particular
node, a child model can be created from the GO graph, but this new child
model also needs data from the original model (its grandparent).  Thus, when
the GO graph creates a child model it needs to ask its parent for the
expression data.
\end{Description}
\begin{Section}{Objects from the Class}
Objects can be created by calls of the form 
\code{new("gAskAncestorMessage", ...)}.
\end{Section}
\begin{Section}{Slots}
\describe{
\item[\code{type}:] which model type to look for as an ancestor (this is a
character string naming the class)
\item[\code{mData}:] the data that is being requested 
\item[\code{from}:] the MVC that asked the question 
}
\end{Section}
\begin{Section}{Extends}
Class \code{"gMessage"}, directly.
\end{Section}
\begin{Section}{Methods}
\describe{
\item[from<-] Sets the \code{from} slot 
\item[from] Returns the \code{from} slot 
\item[mData<-] Sets the \code{mData} slot 
\item[mData] Returns the \code{mData} slot 
\item[type<-] Sets the \code{type} slot 
\item[type] Returns the \code{type} slot 
}
\end{Section}
\begin{Note}\relax
Even though this class is used to ask for information from an ancestor, each
model (MVC) has only parent.  This is important when considering how data
sets are linked.
\end{Note}
\begin{Author}\relax
Elizabeth Whalen
\end{Author}
\begin{SeeAlso}\relax
\code{\LinkA{gMessage-class}{gMessage.Rdash.class}}
\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
\end{ExampleCode}
\end{Examples}

