Versions Compared

Old Version 32

changes.mady.by.user Greg White

Saved on

compared with

New Version 33

changes.mady.by.user Greg White

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 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
Anchor
PRJ-MADTWISSINDB
PRJ-MADTWISSINDB
PRJ-MADTWISSTODB: 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. 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:
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:
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:

  1. Anchor
    PRj-MODELOPTICS
    PRj-MODELOPTICS
    PRJ-MODELOPTICS: Additionally we must create a LIPS application for helping a user submit models to be run (the SCP "Optics" panel)

...

  2. Anchor
    PRJ-MODLEDIAG
    PRJ-MODLEDIAG
    PRJ-MODELDIAG: 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.

...