writeCelHeader          package:affxparser          R Documentation

_W_r_i_t_e_s _a _C_E_L _h_e_a_d_e_r _t_o _a _c_o_n_n_e_c_t_i_o_n

_D_e_s_c_r_i_p_t_i_o_n:

     Writes a CEL header to a connection.

_U_s_a_g_e:

     writeCelHeader(con, header, outputVersion=c("4"), ...)

_A_r_g_u_m_e_n_t_s:

     con: A 'connection'.

  header: A 'list' structure describing the CEL header, similar to the
          structure returned by 'readCelHeader'().

outputFormat: A 'character' string specifying the output format.
          Currently only CEL version 4 (binary;XDA) are supported.

     ...: Not used.

_D_e_t_a_i_l_s:

     Currently only CEL version 4 (binary;XDA) headers can be written.

_V_a_l_u_e:

     Returns (invisibly) the pathname of the file created.

_R_e_d_u_n_d_a_n_t _f_i_e_l_d_s:

     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. 'readCelHeader'().  The redundant
     information is in the (CEL v3) '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.

_A_u_t_h_o_r(_s):

     Henrik Bengtsson (<URL: http://www.braju.com/R/>)

