...

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.