This note attempts to describe the production of the so called ``cooked'' data for the e1, g1 and g6 data sets. The authors offer it as a model for processing all run periods' data. The production of ``cooked'' data involves more than providing users with files of reconstructed data. The software and procedures must ensure the proper calibration of the reconstructed data, the quality of the reconstruction code used, and the repeatability and documentation of the entire operation. These goals are achieved through the use of the software and procedures described in this note.
The first part of this note is intended to provide motivation for the note and a description of the design philosophy used in the development of the ``cooking'' procedures. The next section describes the databases used to steer the cooking of the data and asses the quality of said processing. Following that, the various programs developed for the processing of the e1, g1 and g6 data sets are itemized and the cooking script used for processing is described. This note concludes with a discussion of the steps required to produce a ``cooked'' data set using the described procedures.