GC Scalability Test Federation

[dave zimmerman <zimm@sseos.lbl.gov>]

I have made up a 2% fraction of the test federation on starsu00.  I
welcome any comments or suggestions on its structure.

Each event in the federation consists of 6 components

component name                    file size                       Number
of Runs per file
***************                *********               ************
Event
130Meg                                1
hit
600Meg                                2
trk
600Meg                                4
ebe
600Meg                                 1
raw1
600Meg                                1
raw2
600Meg                                1

Each run consists of 10,000 events.  Note that the Trk and Hit component
files each cover more than one run.

The file names for each run/component are descriptive as can be seen
from the directory listing:
starsu00 505% ls -last RUN13*
245056 -rw-r--r--   1 zimm     rhstar   250798715 Jun 15 16:06
RUN13.raw1.dat
245056 -rw-r--r--   1 zimm     rhstar   250798715 Jun 15 16:06
RUN13.raw2.dat
128024 -rw-r--r--   1 zimm     rhstar   131019202 Jun 15 13:43
RUN13.Event.root
589432 -rw-r--r--   1 zimm     rhstar   603270009 Jun 15 10:05
RUN13_16.Trk.root
588512 -rw-r--r--   1 zimm     rhstar   602328602 Jun 15 10:01
RUN13_14.Hit.root
588376 -rw-r--r--   1 zimm     rhstar   602190568 Jun 15 09:55
RUN13.Ebe.root

The DST objects (Ebe, Trk, Hit) are very simple.  Basically just:
RunNumber,
EventNumber
a large array of random floats.

The "Event" component for an event is the entry point for an analysis.
It has the run number and event number information.
It also has the sequence number in the root tree (file) for the hit, trk
and ebe components which correspond to the particular event.

The programs used to create each of the files and the data created with
those files can be found in;
starsu00 516% pwd
/data03/zimm/Event/prod
starsu00 517% ls
Event/   Reader/  bin/     data/    ebe/     hit/     raw/     trk/
starsu00 518%

The Reader/ directory contains some code to open up the event component
and look around.
The bin/ contains the executables used to generate the data found in
data/
The directories named after the components contain the code used to
create the components