SwissFEL Controls Architecture

[Greg White <gregory.white AT psi.ch>]

Colleagues,

Please find below the agenda for our SwissFEL architecture meeting, in the 
time
slot vacated by the SwissFEL meeting.

Location: WBGB 21 (note, not 19, where the SwissFEL meeting is usually held)
Date/Time: 18.04.13 10:00-11:30

Cheers
Greg

Agenda and material
-------------------

The agenda will be to review the basic architecture proposal for application
level systems, as first outlined by Elke, Leo, Sven, Timo and Greg (me). 
I'll give a short talk and the basic architecture diagram. 

The architecture so outlined is composed of:

1. EPICS IOC Core doing controls and diagnostics

2. EPICS V4 services for getting scientific data in matlab and other apps:

   + Timing pulse data acquisition service (1 device acquired over many beam 
pulses),
     for phase related acquisition, eg BPM buffered acquisition
   + Synchronized timing pulse data acquisition service (M devices acquired 
over
     1 beam pulse, or small number N beam pulses), such as for bpm orbit 
acquisition.
   + Online model service based on MADX for transverse optics 
   + Possibly others specialized model services for beginning of machine 
(space-charge 
     dominated), longitudinal dynamics and others
   + Directory service, for programs for find devices in a given kind in a 
given 
     accelerator area. Eg to help build the list of bpms for a bom orbit 
request
     from the Synchronized timing pulse data acquisition service above. 
Probably
     based on "findrecord"
   + Oracle service, giving access to Oracle from matlab, caQtDm etc. 

3. Oracle for static data, such as device names, magnet calibrations, magnet 
polynomials

4. Archive service, or services, as a whole able to archive pulse identified 
accelerator
diagnostics and detector images! Whether this is an extension of the basic 
EPICS archiver,
or involves a new archiver development, is not decided. If it involves a new 
one, would
that new one be based on the SLAC or BNL or somewhere else's developments, is 
not decided. 

5. Error logging. Basic technology for this must be decided.

6. caQtDM for "synoptic" displays.

7. Matlab for apps. Compiled or not?

8. A Launcher for apps and a remote daemon manager for services.
 
9. Alarm handler and viewer

10. striptool