Operation of CODA Run Control - Fall 2015

A new VME crate has been loaned to us by JLab. This is a non-VXI crate, and it came with a single CAEN V792 integrating ADC module instead of the fADC250 that we were using for tests in 2013-2014. These changes have required us to go back to the start and reconfigure a CODA daq runtime that works with the fall 2015 setup. Some things have not changed relative to what is described in Procedure for Operation of CODA Run Control - Fall 2013.

1. the ROC is still at 137.99.19.12 (halldtrg5.phys.uconn.edu, also called guest2.phys.uconn.edu)
2. the userid for running CODA is still halld (see R. Jones for pw)
3. we are still running CODA version 2.6.1 (see /usr/local/coda/* for version info)
4. we are still running the "micro_test" configuration in the msql database
   • one readout controller called TROC5
   • one event builder called EB5
   • one event recorder called ER5
5. we are still configured to write output data to /home/halld/data which is mounted on /nfs/direct/annex2/TAGM-tests on the cluster

The updated procedure for taking a run using the pulser trigger is as follows.

1. Log on to halld@halldtrg5.phys.uconn.edu using ssh -X to forward X11 windows to your desktop. To check that X11 forwarding is working, issue the "xterm" command, verify that it pops up on your desktop, then kill it. Verify after login that your shell defaults to the /home/halld/ directory.
2. Ensure that the msql daemon is NOT running by typing "ps -efw | grep msqld" and kill it (pkill -9 msqld) if it is.
3. Set the proper environment variables by typing "source micro/coda_micro_setup". These environment variables include EXPID and SESSION, which can be changed to accommodate different run control set-ups. You should see the following message: "Setting up coda 2.6.1 from /usr/local/coda/2.6.1 AFECS Home set to /usr/local/coda/2.6.1/Afecs-1.4 done."
4. Clear the desktop of unwanted windows, and start the CODA runtime with the command "./start_daq.sh" and watch all of the pretty colored windows popping up on the desktop. Check for errors and warnings in each one as it starts.
5. Go to the run control gui window and select "Connect" under the "Platform" menu. The Configure button should light up.
6. Click the "Configure" button that appears below the "Platform" menu (farthest to the left). After a moment, the event builder, read-out controller, and event recorder should appear in the table in the center of the gui, as EB1, TROC5, and ER1. You should see messages at the bottom indicating that the configure started and has succeeded.
7. Click the "Download" button immediately to the right of the "Configure" button. By now, the run parameters Expid, session, and configuration should be displayed.
8. Click the "Prestart" button immediately to the right of the "Download" button.
9. Click "Start" to begin the run. Take care to note any warnings or errors, shown in the bottom message display.