From notes 02-10-2015

For all tests we will run all DAQ software from clondaq3 as "clasrun" (default password). 

Login in to that machine sets up the coda environment automatically.

Software for current release is  at /usr/clas12/release/0.2. Environment variable  $CLAS12 points to the release. 

CODA software: $(CLAS12)/coda
SVT DAQ software: $(CLAS12)/slac_svt

The config file for the SVT DAQ is read from  /slac_svt/daq/config/clasdev.cnf. It can be overridden if another config file is specified. 

CODA setup
Database: "clasdev"
Session: "clashps1"
Configuration: "hps3_noer"

Sync event
When daq is running with sync events enabled the sync flag is sent last in a block of triggers (the frequency is tunable) in last event in a block. The ROCs should readout all events and acknowledge. An error bank can be sent if there is a problem to flag for offline processing.  

Event size limitation
The problem we had with event builder complaining about event size begin too big can probably be fixed by increasing the event size with '-s' parameter to the ET system. The number events might need to be lowered to handle very large event sizes. For example,  

et_start -n 5000 -s 200000 -f file

Our event size in calibration is approximately 12.5kB/hybrid or 450kB/event for the whole SVT.

Data format
Sergey will do disentangling on 2nd readout list so that event format will look like the final one. Ryan will work on doing this in the firmware instead to avoid the extra overhead. One thing to note is that the event format has a header that is "bank of banks" and doesn't seem to follow the latest evio format. It has a sync flag that needs to be filled (function from TI master) in bank of banks header for every event.

Running CODA on clondaq3

Begin by logging into clondaq3 as user "clasrun" (ask expert for password).  This will run login scripts that will setup all environmental variables required to run CODA.  CODA can then be started by issuing the following command from a terminal window: 

hpsdaq3_start

This will pop up the event builder, the event recorder, ET ring, run control (RC) GUI and an xterm for each of the DPM's and DTM's.

hpsdaq3_stop

From the RC GUI, click 'Connect' to connect to the RC server followed by 'Configure'.  This will pop up a dialog that allows you to choose a run type.  For our current setup, two configurations can be chosen:

1. hps3 :  Used to run when writing events is desired
2. hps3_noer : Used to run without writing events

At this point, you would also typically choose a configuration file by pressing 'Config' and specifying the path.  However, if the configuration file is not selected, a default configuration is loaded (hps10). Once the run type and configuration are selected, pressing 'OK' brings you back to the RC GUI.  From here, pressing 'Prestart' followed by 'Go' starts the run.

Once the run has been started, software triggers can be sent by issuing the following command from a terminal:

tcpClient hps10 'tiSoftTrig(1, 1, 0, 0)'

The second argument in the command tiSoftTrig allows you to set the number of triggers to send.