Page History

...

This will proceed in 4 phases:

Phase 0: SLC Modelling System.

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 for new (matlab) applications and ad-hoc analysis in matlab.

Anchor
PRJ-ADDFILEMODELDATA PRJ-ADDFILEMODELDATA

PRJ-ADDFILEMODELDATA: Add to the model data acquisition already in Aida, the ability to get QUAD, BEND etc data from SLC model output file.

Phase 1: Put Mad model run results in the Oracle database.

Anchor
PRJ-MADTWISSINDB PRJ-MADTWISSINDB

PRJ-MADTWISSTODB:

...

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. In this phase we will architect the model hierarchy - how one or more model sections comprise a beamline, and the beamline modelled in one or more energy profiles (aka "Twiss modes").

Anchor
PRJ-BDESTOKMOD PRJ-BDESTOKMOD

PRJ-BDESTOKMOD: 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: XAL MODEL

Anchor
PRJ-XALMODEL PRJ-XALMODEL

PRJ-XALMODEL: 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. The model server runs (in XAL language it hall "probe") the input file on demand (design lattice + extant values, design lattice + design settings, test lattice + test settings, or test lattice + extant values). The model inputs for this phase will be a hand written XAL input files. That is to say, this is not a continuous accelerator simulator.

Phase 3: Generate Models from Online DB

Anchor
PRJ-MODLEAUTOGEN PRJ-MODLEAUTOGEN

PRJ-MODELSAUTOGEN: Automatic generation of online "design" models' source files (XAL and MAD) from the Oracle database devices, plus design values in the DB. This

Model Diagnostics

Two model utility applications are needed:

...

This section outlines projects to support the requirement for control setpoint processing ("set") and read data ("get"), for online physics applications.

Control Data

1. Anchor
   PRJ-SAIOCCOMP PRJ-SAIOCCOMP

   PRJ-SAIOCCOMP: Completion of the "SLC Aware IOC" project, and Beam Synchronous Acquisition and Control (BSAC) in particular.

2. Anchor
   PRJ-JCAJNIFIX PRJ-JCAJNIFIX

   PRJ-JCAJNIFIX: 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 #DECN-JNIJCA

3. Anchor
   PRJ-ADDXMLTOAIDA PRJ-ADDXMLTOAIDA

   PRJ-ADDXMLTOAIDA: Add XML data packaging to AIDA. This facilitates trivial structured data display, since AIDA will have prepackaged the data for rendering via a cascading style sheet (CSS) to an xhtml "browser" display (although we won't use a browser in the normally understood sense, we'll use the built in Eclipse browser.

...