In order to run the combined S800 + Gretina daq, the following steps need to be taken:

1. Start up the S800 data acquisition system as you normally would on spdaq19.
2. Log in using the experimental account to ddasdaq3 or any other of the systems dual homed to the GRETINA/NSCLDAQ network.

- godaq starts the Readout control program. - Click the Start button. This will grab remote control over the S800 readout GUI.

 You should now be able to start runs as needed in the experiment's ReadoutGUI running
 on the dual homed system.

When everything has started correctly you should have the following ring buffers in the dual homed system (e.g. ddasdaq3):

* experimental-user-name (e.g. e14045) this ring is where sampled coincidence data

 is placed.  This is done via a tapcat, glom pipeline.

* spdaq19.rawccusb - will provide raw data from the S800 CAMAC crate. * spdaq19.rawvmusb - will provide raw data from the S800 VME crate. * spdaq19.s800filter - will provide the event built, reformated data from the

                     S800. During a run, data are pushed from this ring into the
                     GRETINA GEB.

In addition to the normal stagea are structure three directories are added that will be used to store raw S800 data:

* stagearea/rawccusb - Event files containing raw ccusb data from the s800. * stagearea/rawvmusb - Event files containing raw vmusb data from the s800. * stagearea/s800filter - Event files containing event build, reformatted

                        s800 data.

1. On spdaq48 in /user/s800/operations/daq/usb/TclXXUSB do:

wish ./RunControl.tcl

or, on devop2 (the S800 MAC machine)

click on the operations folder on the lower icon bar and select runcontrol.command

2. On a dataU machine logged in as the experimental account (e11007 for the June 2012 testing period) do

godaq

3. On spdaq44 do:

/usr/opt/daq/10.1/bin/ringbuffer status. The output should look similar to:

 +----------------+------------+-------+-------------+--------+---------+---------+------+-------------+
 |Name            |data-size(k)|free(k)|max_consumers|producer|maxget(k)|minget(k)|client|clientdata(k)|
 +----------------+------------+-------+-------------+--------+---------+---------+------+-------------+
 |0400x           |8195        |8195   |100          |-1      |0        |0        |-     |-            |
 |s800            |8195        |8195   |100          |7485    |0        |0        |-     |-            |
 |-               |-           |-      |-            |-       |-        |-        |9143  |0            |
 |segatest        |8195        |8195   |100          |-1      |0        |0        |-     |-            |
 |spdaq48.0400x   |8195        |8195   |100          |17205   |0        |0        |-     |-            |
 |spdaq48.segatest|8195        |8195   |100          |-1      |0        |0        |-     |-            |
 +----------------+------------+-------+-------------+--------+---------+---------+------+-------------+

Upon start of run there will be another client of the s800 ring, which is the pushToGEB process. This should die on end run.

The S800 daq will now be in slave mode, and run control is done from the NSCL daq window.