Production Exe: 3.3.1 MDC1-Patched version
tcl master file:  run_Production.tcl.master_3.3.1
Reconstruction log files are in the following places (include stdout, stderr and FBS job summary):

• /cdf/scratch/mirsi@fcdfsgi2
• /cdf/data2/cdfprod0@fnpcc

The following tcl file was used for splitting:  run_MDC_output_Stream_B.tcl

The following graphs show the activity and some statistics at the Farm:

• Stage and run activity (x is the day in January 2000, y is the number of files)
• Split/soncatenation activity (same axis)
• Run time per event (average over the file) for the reconstruction and for the SiPaternRec module.

fname: file name that was reconstructed (Raw data Table) or was splitted (Production data Table). Actually the name in the Production data Table is just name in the Raw data Table + FBS job id and FBS process number, so we know what FBS job was responsible fro the production.

ndname: node name - i.e name of the worker node that was used for the reconstruction

fstatus: status of the processing, DONE means that it went through the whole chain

incfsize: size of the inclusive file

stime: stage time, time when the file was staged from the tape

rtime: reconstruction time, i.e. time when reconstruction was finished

rfsize: raw data file size, i.e. size of the input to the farms

lostevnts: now it is the last reconstructed event, In case that the value is NULL or 0, all of the events were reconstructed successfully in this data file.

exe_version: not yet available

FBS_id: FBS job id, added lateler than MDC1

FBS_proc: FBS proccess number, added lateler than MDC1

num_of_proc_time: number of reconstructions, added lateler than MDC1

fdatime: time of the concatenation

dataset: dataset id, to which the file belong

fileset: fileset that the raw file was staged from

low_run_section: lowest run section for the files

high_run_section: highest run section for the file