\HeaderA{writeCelHeader}{Writes a CEL header to a connection}{writeCelHeader}
\keyword{file}{writeCelHeader}
\keyword{IO}{writeCelHeader}
\keyword{internal}{writeCelHeader}
\begin{Description}\relax
Writes a CEL header to a connection.
\end{Description}
\begin{Usage}
\begin{verbatim}writeCelHeader(con, header, ...)\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{con}] A \code{\LinkA{connection}{connection}}.
\item[\code{header}] A \code{\LinkA{list}{list}} structure describing the CEL header, similar
to the structure returned by \code{\LinkA{readCelHeader}{readCelHeader}}().
\item[\code{...}] Not used.
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
Currently only CEL v4 headers are supported.
\end{Details}
\begin{Value}
Returns (invisibly) the pathname of the file created.
\end{Value}
\begin{Section}{Redundant fields}
The CEL v4 header contains redundant information. To avoid inconsistency
this method generates such redundant values from the original values.
This is consistent to how the CEL reader in Fusion SDK does it, cf.
\code{\LinkA{readCelHeader}{readCelHeader}}().  The redundant information is in the (CEL v3)
\code{header} field, which contains the CEL header information as it
would appear in the CEL v3 format.  This in turn contains a DAT header
field reproducing the DAT header from the image analysis.  It is from
this DAT header that the chip type is extracted.
\end{Section}
\begin{Author}\relax
Henrik Bengtsson (\url{http://www.braju.com/R/})
\end{Author}

