Step 2: Pass 0 (calibration pass)

The purpose of the first formal pass through the data is twofold: first to analyze enough events to fully calibrate the time of flight system with pions, and second, to provide a data set with which people can refine analysis codes and the calibrations. Because this is a formal pass through the data which will serve as a reference for later analysis the following procedure should be followed before analyzing this pass:

• Construct a tagged software library: It is important to know exactly what version of the software was used to process the data, when problems are found in the cooked data files we must be able to refer back to the software used to create the files. These libraries should be identical the standard libraries. Other users should also be able to link their software to these libraries.
• Build a set of analysis, calibration, monitoring and utility executables from the tagged software library: Obviously, all the executables used during the cooking process must use the tagged software libraries.
• Freeze a version of the CLAS_PARMS area: Again, one must have a record of all of the ingredients used to construct the processed data file, the calibrations are a major source of input into the processing code.
• Tag the version of the processing scripts: Each of the elements of the processing scripts contain hard-coded executable commands with certain flags set. In order to keep an accurate record of how the data was processed a version of these scripts must be saved also.
• Processes selected runs.
• Copy all files, libraries and executables to tape silo: The final step in the process is to document everything you have done by archiving all the files needed for and produced by the cooking procedure to the tape silo.