How to run mureco
-----------------

I. Building mureco-exec

(1) Log on to d0chb.

Do the standard setups.
(2) setup D0RunII test
(3) setup d0cvs

To fetch mureco package from cvs, do:
(4) mkdir workdir
workdir is your working directory.
(5) newrel -t test test
This command creates directory called test with all the cvs goodies.

To get mureco package from cvs, do:
(6) cd test
(7) addpkg -h mureco

To compile and link, invoke GNUmake by doing:
(8) gmake
This might take one hour or more, depending on how busy d0chb is.

When it's done, you have everything you need to run mureco. An executable
image called mureco_test is in workdir/test/bin/IRIX6-KCC directory.

To run mureco, you need rcp files. They are in workdir/test/mureco/test
directory. Copy them to workdir/test directory or set path to
workdir/test/mureco/test and type:

mureco_test mureco_test

Your program starts running and spitting out countless meaningless messages.

If you are interested in what you are reading, look at ReadEvent.rcp file. It
has a string input variable InputFile that tells you what file you are reading.

The latest version of mureco consists of three reconstructors; MuoHitReco,
MuoSegmentReco, and MuoTrackReco. MuoHitReco reads and processes digitized hit
chunks in DSPACK format. The current default input file in ReadEvent.rcp is an
output from d0gstar and does not have digitized hit chunks. It has only
SimMUONHit chunks. When mureco_test is run on this file, the program looks for
digitized hit chunk (MuoDigiChunk). If it does not find one, it simply skips
the execution of code that deals with hit processing. In order to really test
mureco, you have to use input files with MuoDigiChunk in them. The files with
MuoDigiChunk are generated using muo_digi package (reconstructor: MuoDigiReco).


II. Building muo_digi-exec

(1) Follow the steps (4)-(8) in I., substituting muo_digi for the package.

(2) To run muo_digi, you need rcp files. Copy them from test directory. Specify
your input file in ReadEvent.rcp and an output file in WriteEvent.rcp.

muo_digi_test muo_digi_test

will run the program.

In the next release of d0gstar-simpp package, muo_digi will be included in the
exec module. You will not have to run muo_digi separately on d0gstar output
files. But for now, you have to do this step.


III. Running d0sgtar exec to generate MC events

You can generate your own MC events by running d0gstar_user package.
See directory /d0dist/dist/packages/d0gstar_user/devel/ex03. This directory
contains a shell script example.csh and necessary rcp files. When you run
d0gstar-simpp, don't turn on SimKEYPHitChunkGen in the current version. It
fails assertion.


                                                    - Taka