1. Coda-Epics communications have changed in Coda 2.0...now I
believe we should only use the CDEV interface to Epics (from run
control, etc.).
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?
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?
Sincerely,
Elliott