The problem we have now is that Monitor and Recsis are not started
automatically as part of DAQ procedures. So below I give descriptions of
how to do that. I'll add this to the monitoring documentation if I get a
chance, or at least just put a copy of this message there.
To run monitor, follow the steps:
1. log onto clon00
2. cd ~clasrun/mon
3. type "setenv DC_NAME clasprod"
4. type monitor
That terminal window will be tied up with monitor until the run ends.
Leave it alone. Especially don't ^C in it.
Now you can monitor from the global section as described in the "Run
Checklist" section of the DC Monitoring document.
When the run is ended, your monitor session will exit and write a
monVWXYX.hbook, which can be used as described in the "Shift Checklist"
section of the DC Monitoring document. You have to start monitor again
for the next run.
I'm not sure how to get recsis_online going, but I deposited a user_ana
image on the clon and made a clon.cshrc. As soon as a run is started you
can start reconstruction analysis on it (as long as go aren't skipping a
bunch events) by following these steps:
1. log onto a clon computer other that clon00
2. cd ~clasrun/recsis/run
3. source clon.cshrc
4. edit dcinit.tcl to reflect the data file you want to analyze
5. type "user_ana -t dcinit"
6. when you get the "Do it>" prompt, type "go 4000" to analyze 4000 events
7. when the "Do it>" prompt reappears, type exit
8. look in the termination messages to see the name of the rzn file:
rennnn.rzn where nnnn is some number
9. type "mv rennnn.rzn ../../mon/rec0mmmm.hbook" where nnnn is the number
you determined in step 8 and mmmmm is the run number
Now that the recsis hbook file exists, you can follow the monitoring
procedures.
Enjoy
\ R A Thompson /
/ Dept of Physics and Astronomy University of Pittsburgh \
\ Pittsburgh, PA 15260 /
/ richardt@cebaf.gov 757-269-7475 \