\HeaderA{writeTpmap}{Writes BPMAP and TPMAP files.}{writeTpmap}
\aliasA{tpmap2bpmap}{writeTpmap}{tpmap2bpmap}
\keyword{file}{writeTpmap}
\keyword{IO}{writeTpmap}
\begin{Description}\relax
Writes BPMAP and TPMAP files.
\end{Description}
\begin{Usage}
\begin{verbatim}
writeTpmap(filename, bpmaplist, verbose = 0)

tpmap2bpmap(tpmapname, bpmapname, verbose = 0)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{filename}] The filename.
\item[\code{bpmaplist}] A list structure similar to the result of \code{readBpmap}.
\item[\code{tpmapname}] Filename of the TPMAP file.
\item[\code{bpmapname}] Filename of the BPMAP file.
\item[\code{verbose}] How verbose do we want to be.
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
\code{writeTpmap} writes a text probe map file, while
\code{tpmap2bpmap} converts such a file to a binary probe mapping
file. Somehow Affymetrix has different names for the same structure,
depending on whether the file is binary or text. I have seen many
TPMAP files referred to as BPMAP files.
\end{Details}
\begin{Value}
These functions are called for their side effects (creating files).
\end{Value}
\begin{Note}\relax
\end{Note}
\begin{Author}\relax
Kasper Daniel Hansen <khansen@stat.berkeley.edu>
\end{Author}
\begin{References}\relax
\end{References}
\begin{SeeAlso}\relax
\code{\LinkA{readBpmap}{readBpmap}}
\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
\end{ExampleCode}
\end{Examples}

