Page History

Setting up CODA to run

First, the event builder, event recorder and ET ring can be started by issuing the following commands from a terminal:

cd 

Starting from scratch

Open new terminal

...

/u1/coda_rth

...

./start_coda_

...

Open new terminal

...

xterm.csh 

This will open a dedicated (blue) xterm for each of the processes above.  It will also open a terminal with a connection to the TI.  This will require a password which can be retrieved from one of the SVT DAQ experts. 

cd /u1/coda_rth

...

sudo ./start_eb 
sudo ./start_

...

er
sudo ./start_et

Once the event builder, event recorder and ET ring have started up successfully, the run control can be started as follows: 

sudo tcsh
su -l **** (DAQ expert user name)
cd 

Open new terminal

...

/u1/coda_rth

...

/
./start_

...

Open new terminal

coda_xterm_rc.csh

cd 

...

/u1/coda_rth

...

./start_

...

rc 

...

...

...

Connect to DTM/DPM and start ROCs:  in .  

There is a script that pops up all windows in xterms:
$ cd /u1/coda_rth
$ ./start_rce.csh 

$ cd /u1/daq
$ source setup_env.csh 
$ ./rceScripts/connect_host <slot> <?> <?> (FIX NAMES OF ID's)
$ /mnt/host/coda/run_roc 

Start rce server on dpm7

GUI if not running:

$ cd /u1$ ssh dpm7
$ cd /mnt/host/daq
$ ./rceScripts/start_servergui.csh

If it fails to connect check that server is running on dpm7 and restart if needed

$ ssh dpm7Start rce GUI 
$ cd /mnt/u1host/daq
$ ./rceScripts/start_guiserver.csh

Click 'connectConnect' on RC GUI.  Click 'configureConfigure' then select '8rces' as run type.  Click 'Config' and select '/u1mnt/host/coda/rcetest0svtrce0.cfgcnf'.  Click 'OK'.

At the moment, during the 'Configure' stage, the configuration file svtrce0.cnf is being overwritten. In order for things to work properly, the overwritten file needs to be replaced with a backup after the configuration has taken place.  To do this, issue the following command in a terminal: 

sudo cp /u1/cob_nfs/host/coda/svtrce0.cnf.save /u1/cob_nfs/host/coda/svtrce0.cnf

Click 'Download'. 'Prestart' button appears if things worked.

Go to TI and Reset (but don't start sending triggers)

Click 'Prestart'.

Click 'Go'.

Go to TI and start sending triggers.

Trigger setup

Option 1: Send software triggers from TS

Open new terminal.

$ cd /u1/daq & soruce source setup_env.csh
$ ./rceScripts/connect_ti.csh (pw ask Pelle/Ryan/Ben)
$ cd /home/daq/linuxvme/tid/src ti/test
$ ./tidInt_test

Change trigger rate by modifying tidInt_test.c: tidSoftTrig(0xffff,0xFFFF,1);

tiLibTest

Option 3: Send software generated triggers with new software from

...

TS from  function generator

TBI

...