\HeaderA{parseGEO}{Parse GEO text}{parseGEO}
\aliasA{parseGDS}{parseGEO}{parseGDS}
\aliasA{parseGPL}{parseGEO}{parseGPL}
\aliasA{parseGSE}{parseGEO}{parseGSE}
\aliasA{parseGSM}{parseGEO}{parseGSM}
\keyword{IO}{parseGEO}
\begin{Description}\relax
Workhorse GEO parsers.
\end{Description}
\begin{Usage}
\begin{verbatim}
parseGEO(con, GSElimits)
parseGPL(txt)
parseGDS(txt)
parseGSE(con, GSElimits)
parseGSM(txt)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{txt}] The text from a GEO SOFT format file
\item[\code{con}] A connection that contains the body of a GEO SOFT format file
\item[\code{GSElimits}] Used to limit the number of GSMs parsed into the GSE
object; useful for memory management for large GSEs.
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
These are probably not useful to the end-user.  Use getGEO to access
these functions.  parseGEO simply delegates to the appropriate specific parser.  There
should be no reason to use the parseGPL, parseGDS, parseGSE, or
parseGSM functions directly.
\end{Details}
\begin{Value}
parseGEO returns an object of the associated type.  For example, if it
is passed the text from a GDS entry, a GDS object is returned.
\end{Value}
\begin{Author}\relax
Sean Davis
\end{Author}
\begin{SeeAlso}\relax
\code{\LinkA{getGEO}{getGEO}}
\end{SeeAlso}