Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

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:

Code Block
languagebash
cd /u1/coda_rth
./start_coda_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. 

Info
titleNote

Running the script start_coda_xterm.csh is equivalent to running the following commands with some additional options:

Code Block
languagebash
cd 

Starting from scratch

 

Open new terminal

...

/u1/coda_rth

...

Open new terminal


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: 

Code Block
languagebash
sudo tcsh
su -l **** (DAQ expert user name)
cd /u1/coda_rth/
./start_coda_xterm_rc.csh
Info
titleNote

Running the script start_coda_xterm_rc.csh is equivalent to running the following command with some additional options:

Code Block
languagebash
cd 

...

/u1/coda_rth

...


./start_

...

Open new terminal

...

rc 
Warning

When running using Sergey's binaries

...

, the symbolic link /usr/local

...

needs to be pointing to /usr/new_local

...

. This symbolic link is destroyed every night by Taylor so it needs to be set once daily. 

Connect to DTM/DPM and start ROCs.  

There is a script that pops up all windows in xterms:

$ ./start_eb

Press 'connect' on RC GUI.

Open new terminal
$ cd /u1/coda_rth
$ ./start_ebConnect to DTM/DPM and start ROCs rce.csh 

Or manually in separate tabs/terminals

$ cd /u1/daq
$ source setup_env.csh 
$ ./rceScripts/connect_host <slot> <rce> <id> <?> <?> (FIX NAMES OF ID's)

Start control server on DPM7 if not already running


$ /mnt/host/coda/run_roc 

Start rce GUI if not running:

$ cd /u1/daq
$ $ ./rceScripts/start_gui.csh

 

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

 

$ ssh dpm7connect_host 1 3 2
$ cd /mnt/host/daydaq
$ ./rceScripts/start_server 

Start rce GUI

server.csh

 

Click 'Connect' on RC GUI.  Click 'Configure' then select '8rces' as run type.  Click 'Config' and select '/mnt/host/coda/svtrce0.cnf'.  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: 

Code Block
languagebash
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

$ cd /u1/daq
$ & source setup_env.csh csh
$ ./rceScripts/start_gui.shconnect_ti.csh (pw ask Pelle/Ryan/Ben)
$ cd  ti/test
$ ./tiLibTest

Option 3: Send software generated triggers with new software from TS from  function generator

TBI 



Layout group C on 8/27/2014
Hostslotrce?id?
dtm410
dpm0100
 102
 110
 112
 120
 122
 130
dpm7132

...

...

1

...

   `$ATCA_IP $ATCA_SHELF/1/0/2 --ifname $ATCA_IFNAME` \

   `$ATCA_IP $ATCA_SHELF/1/1/0 --ifname $ATCA_IFNAME` \

   `$ATCA_IP $ATCA_SHELF/1/1/2 --ifname $ATCA_IFNAME` \

   `$ATCA_IP $ATCA_SHELF/1/2/0 --ifname $ATCA_IFNAME` \

   `$ATCA_IP $ATCA_SHELF/1/2/2 --ifname $ATCA_IFNAME` \

3

...

...

2

...

   

Run TS

Send software generated triggers:

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

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