Cold Start of CODA

If CODA is not running, or if it gets hung up, you can do a cold start. Frequently a subset of these steps is sufficient to recover from a hangup, but it takes some experience to realize the minimum of steps that are necessary, so the simplest thing is to do them all (it takes a few minutes).

• Kill off all CODA processes on the workstation by typing ``kcoda''. This stops runcontrol, the event builder, and other processes, and allows for a clean start.
• Make sure the fastbus and VME crates are running. The crates are named below as ``computer(CODA-name)'', where computer is the internet name and the CODA-name is the name runcontrol calls it: hallasfi1 (ROC1), hallasfi2 (ROC2), hallasfi3 (ROC3), halladaq1 (TS0), halladaq4 (TS1), hallavme2 (ROC15), and hallavme1 (ROC14). (Note: for 1-TS mode you don't use ROC15, and sometimes ROC3 which has FPP is left off for good reasons.) You can check if the ROCs are up by looking on the Components work space at the telnet session (if it's not logged, try to telnet in). If the ROCs don't talk to runcontrol, you can type ``reboot'' at the arrow prompt ($\rightarrow$). If you don't get this arrow prompt, or if you can't telnet in, the computer is hung up, so press for a full 5 seconds the labeled green button corresponding to this ROC in the middle room of the counting room. After the ROC comes back (2 minutes), telnet back in to verify it's up.
• Start runcontrol interactively by typing ``runcontrol''. Iconize and ignore the window from which you started runcontrol.
• In runcontrol, press the ``Connect'' button. After ``connect'' wait 10 seconds and press ``Run Types''. You may also press the ``Reset'' button in the upper left corner. Indeed sometimes reset is all that's needed to fix CODA. Choose the run type from the dialog box (see section on Running CODA for descriptions of run types).
• After you configure and download the Run Type, you can ``Start Run'' to start a new run.