Editing Kyle (section)

== Starting and Killing CODA ==

=== What needs to run? ===

In order to properly start CODA one must first run the following processes:

<span style="color:blue">'''Hint:''' Make sure that each of these processes is run independently in their own shell. </span>

1. To start database (new terminal): $ msqld

<span style="color:blue">'''Hint:''' Leave the database running, it does not need to be turned off. </span>

2. Remove session file (new terminal): $ rm /tmp/et_sys_$SESSION

<span style="color:blue">'''Hint:''' This file needs to be removed every time '''et_start''' is run. However, if the file has never been created, it will throw an error. It is okay to ignore this. </span> 

3. Begin the event transfer system(same terminal that you removed the session file in): $ et_start

4. Start the run control platform (new terminal): $ rcplatform

<span style="color:blue">'''Hint:''' Some time is needed for rcplatform to fully boot (about 5 seconds). Upon first running rcplatform, two prompts (within the rcplatform window) will ask the user if it is okay to start.</span> 

The next three steps allow the user to actively see the event builder, event recorder, and the readout controller. (Helpful for debugging)  

5. Start event builder (EB) (new terminal): $ coda_eb_rc3 -i -s $SESSION -name EB1 -type CDEB

6. Start event recorder (ER) (new terminal): $ coda_er_rc3 -i -s $SESSION -name ER1 -type ER

7. Start readout controller (ROC) (new terminal): $ ssh -t root@jlabvme coda_roc_rc3 -i -s $SESSION -name ROC1 -type ROC

<span style="color:blue">'''Hint:''' In step 7, the ROC must be accessed remotely using the ssh protocol.</span>

8. Start the graphical interface for the run controller (new terminal): $ rcgui

=== Bash Scripts === 

Location: '''Computer:''' jlabdaq '''User:''' coda '''Directory:''' ''home/coda/bin''

Small programs can be written in order to quickly start and end CODA in an efficient manner. To accomplish this, multiple terminals must be running in order to start various programs. Terminal emulation programs can easily solve this problem. 

Xterm is the emulator that we chose to use. 

1. StartCODA

<span style="color:green">'''Link:''' [[Setup Files#Startcoda Script|Startcoda Script]]</span>

Within the script xterm can be utilized to run multiple processes in the background. 

Example: '''xterm -bg white -fg black -geometry 96x12-0+192 -e $SHELL -c '$SHELL -c "echo Starting rcplatform; rcplatform"; read' &'''

The ampersand at the end lets the computer know to keep the process running without ending it when the script ends. Similar lines can be written in order to run all of the necessary processes.    

2. KillCODA 

<span style="color:green">'''Link:''' [[Setup Files#Killcoda Script|Killcoda Script]]</span>

Once one is ready to close CODA, a simple script can be written to end all of the processes in an orderly fashion. 

Example: '''ps wwwaux | grep rcplatform | awk '{print $2}' | xargs kill -9 &'''

Here is a statement that lists all running processes, finds the specific name, grabs the process ID, and then kills that process. This can be done for each process that was started.