The KISS runcontrol

RunControlSoundServer

Users Guide

1. http://www-hades.gsi.de/~hadaq/doc/aug04/daqop.html Current Documentation for the DAQ operator
2. MEDM Reference Manual
3. Alarm Handler Users Guide - alh1.2.10

Developers Guide

1. Record Reference Manual
2. The EPICS genSub Record Reference Manual
3. The sseq record
4. IOC Application Developer's Guide R3.14.5
5. State Notation Language and Sequencer Users’ Guide
6. Source Code Documentation of RunControlIOC

Administrators Guide

Currently, quite a few different systems and technologies are involved in delivering data to the run control users interface. Hopefully this may be consolidated some time. In the meantime, here is a short overview.

Trigger

Trigger Rates and Busy are monitored by an EPICS IOC on r2f-35. Up to now, this IOC is called foo, not a really good name, but I just start to understand the EPICS naming and directory scheme.

This IOC is monitored by a script check_run_agent, which restarts the IOC if it fails. This script itself is called every 10 seconds by the program every, which itself is started during system boot by the script $HOME/etc/rc. This means, that the IOC is started and monitored automatically during system boot. Normally, no intervention should be necessary. On the other hand, if you want to get rid of foo, don't kill the foo process itself, but the every. Remark: The predessor of the IOC (the "Channel Access Server") and also early versions of the IOC itself were quite unstable, therefore this complicated procedure was introduced. The reason for the instability seems to be found and fixed, so the whole stuff may be replaced by a simple start of the IOC during system boot.

Event Builder

File Status and Event Rates are monitored by an EPICS IOC in the event builder itself. IOCs under linux normally show up with the process name st.cmd.
This IOC is now also started and monitored via the cron daemon, so do not press the button "Run IOC" any more.

File Status and Event Rates are monitored still by a "Channel Access Server (old style :)" called run_agent on hadeb02. Due to the already mentioned stability problems, this is monitored and restarted by a script called watched_run_agent, which itself is started every minute via the cron daemon. Additionally, since the file name cannot be gathered by the run agent, it is extracted from the parameters-store-file eb_s.tcl by the script feedEpics. This is also started every minute by cron. Again, everything is started and monitored automatically. In case of problems, you need to remove the corresponding lines from the crontab by using the command =crontab -e=. Since the EPICS component on the event builder is only a Channel Access Server, it is accompained by an IOC that runs under the "scs" account on lxi015. IOCs under linux normally show up with the process name st.cmd.
This IOC is now also started and monitored via the cron daemon, so do not press the button "Run IOC" any more.

Oracle

Connection to Oracle run database is done via the tcl_to_ora script.

-- MathiasMuench - 28 Jan 2005