Major Components
This is a basic list of major components in the LCLS applications system. Each of these will require significant requirements and design work. The comments following are only an extreme outline.
Basic Desktop Applications Framework
Architectural and network design.
Installation of basic components; XAL, Eclipse, JCA, Aida, CSS
JCA fixes
Distribution System
Launching displays and external applications
Basic Modelling Environment
This will proceed in 4 phases:
- Phase 0: For BC-1 commissioning, physicists will use the SLC online model system. DIMAD decks generated in the familiar way. The only addition will be to use AIDA's interface to the SLC model system can be used by new (matlab) applications and ad-hoc analysis in matlab.
- Phase 1: Put Mad model run results in the Oracle database. Both "design" and "extant" machine should be supported. Modelling the extant machine will be done by running the mad input through a filter, which will find the epics PV or slc db name associated with each device (via the "symbols" Oracle schema), and create an output file which can be run by Mad. The resulting Twiss and R-mat will then be loaded into Oracle. We will need a "bdes-to-kmod" as part of this. If after analysis that seems hard, we should consider jumping straight to phase 2, since XAL's tracking will acquire klystron readings and make the conversion directly, at the time of tracking, so in this respect it would be easier than implementing an online model system for Mad.
- Phase 2: Functionally as phase 1, but for XAL. Phase 1 precedes phase 2 since we already have a Mad model. Phase 2 will additionally involve adapting XAL for the LCLS beamline requirements (acceleration, solenoid), and creating a model server for XAL.
- Phase 3: Automatic generation of the online model source files from the Oracle database devices.
Model Diagnostics
Additionally we must create a LIPS application for helping a user submit models to be run (the SCP "Optics" panel), and a way to view the twiss and Rmat of a single device, and Rmat "a to b". This is part of phases 1, 2 and 3.
DATA ARCHITECTURE
This section outlines projects to support the requirement for control setpoint processing ("set") and read data ("get"), for online physics applications.
Control Data
- Completion of the "SLC Aware IOC" project, and Beam Synchronous Acquisition and Control (BSAC) in particular.
- Fixes to JCA, using the JNI interface. JCA through the JNI interface to CA must be fixed to be operable within Eclipse. We will not use the JCA interface through CAJ due to other errors which are probably more serious. See Decision on JCA JNI or CAJ
Working Decisions and Standard Practices
We will use the JNI interface of JCA, rather than CAJ interface, until CAJ is fixed. In particular CAJ is reported to easilu overload IOCs and crash them.