>2. Coda 2.0 has its own error logging facility. I don't know what
>the relationship will be between the Coda facility (which is
>primary for run control and many other online tasks) and the Epics
>facility. Perhaps the Coda screen will be primary and the Epics
>screen secondary, perhaps they'll be of equal priority, etc?
FYI:
CEBAF is developing a new error logging facility meant to replace both
the EPICS and CODA facilities. It has been designed with input from
Chip and Graham and a whole host of others. Implementation has started,
with completion by the end of the summer (some parts sooner). It will
have all the capabilities of the CODA 2.0 version, plus a number of
others.
>3. I believe that (eventually) data taking should be stopped
>automatically when serious hardware failures occur. This means
>that Epics processes must be able to communicate back to run
>control (via CDEV) to stop or pause runs when failures are
>detected. Is this possible?
This is easy in principle -- talk to Graham about what interfaces CODA
currently gives you.
Chip